-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
[WIP] add check if lints belong to an external macro #49755
[WIP] add check if lints belong to an external macro #49755
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Manishearth (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Alright, this is a good first step -- now, the LintStore contains a hashmap of future incompatibility lints; we should always lint for these, regardless of the macro. So check the lint id against that. |
Ping from triage @Dylan-DPC! The reviewer requested some changes, could you implement them in the near future? |
Yes sure. Will add them in a few days 👍 |
@Manishearth I don't have access to the |
Ping from triage @Manishearth! The author needs a bit of help. |
Sure you do -- |
This comment has been minimized.
This comment has been minimized.
Ping from triage, @Dylan-DPC ! You have test failures to address. |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Ping from triage @Dylan-DPC! You have other failures to address. |
Thank you for this PR @Dylan-DPC! Unfortunately we haven't heard from you on this in a while, so I'm closing the PR to keep things tidy. Don't worry though, if you'll have time again in the future please reopen this PR, we'll be happy to review it again! |
Oops sorry, got busy and demotivated to complete this. Sure no problems 😄 |
Squash all lints tied to foreign macros by default This PR is a continuation of #49755 (thanks for the initial jump-start @Dylan-DPC!) and is targeted at solving #48855. This change updates the lint infrastructure to, by default, ignore all lints emitted for code that originates in a foreign macro. For example if `println!("...")` injects some idiomatic warnings these are all ignored by default. The rationale here is that for almost all lints there's no action that can be taken if the code originates from a foreign lint. Closes #48855 Closes #52483 Closes #52479
Closes #48855
r? @Manishearth