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
{{ message }}
This repository has been archived by the owner on Dec 27, 2022. It is now read-only.
As we can see from the code, when using the #[proc_macro_hack] attribute to "decorate" a reexport (i.e., in the "declaration crate"), it expects to start parsing
use $implementation_crate_name:ident ::
However, given that we are reexporting from a crate, a way to do this in the 2018 edition (the cleanest way imho, since it avoids any potential path ambiguity), would be to use a leading pair of colons:
As we can see from the code, when using the
#[proc_macro_hack]
attribute to "decorate" a reexport (i.e., in the "declaration crate"), it expects to start parsingHowever, given that we are reexporting from a crate, a way to do this in the 2018 edition (the cleanest way imho, since it avoids any potential path ambiguity), would be to use a leading pair of colons:
That's why it would be great if
proc_macro_hack
in reexport position was changed so that it expects to start parsingThe text was updated successfully, but these errors were encountered: