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
let map = phf_map!{
"foo" => phf_map!{"k"=>"v"}
};
Compile error:
error[E0659]: `proc_macro_call` is ambiguous (macro-expanded name vs less macro-expanded name from outer scope during import/macro resolution)
--> src/main.rs:57:12
|
57 | let map = phf_map!{
| _______________^
58 | | "foo" => phf_map!{"k"=>"v"}
59 | | };
| |_____^ ambiguous name
|
note: `proc_macro_call` could refer to the macro defined here
--> src/main.rs:57:12
|
57 | let map = phf_map!{
| _______________^
58 | | "foo" => phf_map!{"k"=>"v"}
59 | | };
| |_____^
note: `proc_macro_call` could also refer to the macro defined here
--> src/main.rs:57:12
|
57 | let map = phf_map!{
| _______________^
58 | | "foo" => phf_map!{"k"=>"v"}
59 | | };
| |_____^
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
The text was updated successfully, but these errors were encountered:
I stumbled upon this limitation as well. This should at least be documented, so that a potential user of this crate does not invest a lot of time (e.g. to write a code generator for recursive phf data structures) before realising this is not supported.
Compile error:
The text was updated successfully, but these errors were encountered: