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
In my custom-format crate, I pass the special $crate identifier from a declarative macro to a procedural macro, which allows me to avoid using a crate such as proc-macro-crate. This identifier cannot be created with the Ident::new method, so the procedural macro cannot be tested with real inputs using the proc_macro2 crate.
Is it acceptable to extend this crate to allow constructing the $crate identifier via
In my custom-format crate, I pass the special
$crate
identifier from a declarative macro to a procedural macro, which allows me to avoid using a crate such as proc-macro-crate. This identifier cannot be created with theIdent::new
method, so the procedural macro cannot be tested with real inputs using theproc_macro2
crate.Is it acceptable to extend this crate to allow constructing the
$crate
identifier viainstead of panicking ?
The text was updated successfully, but these errors were encountered: