-
Notifications
You must be signed in to change notification settings - Fork 1.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
Add disallowed_macros
lint
#9495
Conversation
r? @flip1995 (rust-highfive has picked a reviewer for you, use r? to override) |
9c1b706
to
77d7b47
Compare
☔ The latest upstream changes (presumably #9525) made this pull request unmergeable. Please resolve the merge conflicts. |
77d7b47
to
a8a0a19
Compare
☔ The latest upstream changes (presumably #9535) made this pull request unmergeable. Please resolve the merge conflicts. |
a8a0a19
to
4229024
Compare
☔ The latest upstream changes (presumably #9516) made this pull request unmergeable. Please resolve the merge conflicts. |
ce89037
to
8b12024
Compare
☔ The latest upstream changes (presumably #7962) made this pull request unmergeable. Please resolve the merge conflicts. |
8b12024
to
86c86c3
Compare
Is this intentionally linting in external macros? |
I wasn't sure which way to go with that, I could see an argument for either way. So for now at least I went with the behaviour of |
Just making sure. Thank you. @bors r+ |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
Closes #7790
Fixes #9558
clippy_utils::def_path_res
already resolved macro definitions which is nice, it just needed a tweak to be able to disambiguate e.g.std::vec
the module &std::vec
the macro, andserde::Serialize
the trait &serde::Serialize
the derive macrochangelog: new lint: [
disallowed_macros
]changelog: [
disallowed_methods
], [disallowed_types
]: Fix false negative when a type/fn/macro share the same path