-
Notifications
You must be signed in to change notification settings - Fork 12.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Macro import does not bring dependent macros in scope in 2018 edition #53811
Comments
I believe this is by design for Edit: The alternative is that clap annotates the dependency macros with |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Importing a macro from a crate in 2018 edition that invokes other macros does not bring those macros in scope. It's easy enough to make work by importing the other macros of course, but surprising behavior anyway, especially when it involves importing macros that won't actually be referenced anywhere in the file itself, only through invocations.
Example (using clap 2.32):
will produce the following error
The text was updated successfully, but these errors were encountered: