Wrong error if a crate exports a macro with the same name as itself #47361
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
A-macros
Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
A-resolve
Area: Name resolution
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
If a crate or module defines a macro with the same name as the crate or module, any type error suggests that you invoke a non-existent macro instead of what you meant to write.
If the macro name is different from the module name then the error is reasonable.
This currently affects the Syn crate. @Arnavion
The text was updated successfully, but these errors were encountered: