-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Don't lint :pat when re-parsing a macro from another crate. #86574
Conversation
r? @jackh726 (rust-highfive has picked a reviewer for you, use r? to override) |
2c31d9a
to
4df9741
Compare
@bors r+ Seems simple enough. |
📌 Commit 4df97419ee19968f7afee2d1307f38b52e267ef7 has been approved by |
Good catch @petrochenkov =) I had thought about assigning you to r+, but I didn't want to overload you. |
r=me with #86574 (comment) addressed and commits squashed. |
218ca9e
to
06db210
Compare
@bors r=petrochenkov |
📌 Commit 06db210 has been approved by |
☀️ Test successful - checks-actions |
compile_macro
is used both when compiling the original definition in the crate that defines it, and to compile the macro when loading it when compiling a crate that uses it. We should only emit lints in the first case.This adds a
is_definition: bool
to pass this information in, so we don't warn about things that only concern the definition site.Fixes #86567