You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's better to have macros being accessed by requiring their full module path, since this allows to avoid naming collision (they could all have the same name) and is more hygienic - instead of all macros being at the root of the crate. That is, the macros should be "usual items", that could be pub etc.
#![feature(pub_macro_rules)] seems to be interrupted, but it should be tracked.
Tracking issue for this feature: rust-lang/rust#78855
The text was updated successfully, but these errors were encountered:
It's better to have macros being accessed by requiring their full module path, since this allows to avoid naming collision (they could all have the same name) and is more hygienic - instead of all macros being at the root of the crate. That is, the macros should be "usual items", that could be
pub
etc.#![feature(pub_macro_rules)]
seems to be interrupted, but it should be tracked.Tracking issue for this feature: rust-lang/rust#78855
The text was updated successfully, but these errors were encountered: