-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Force warnings even when can_emit_warnings == false #86572
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
09d9dc8
to
f939d70
Compare
☔ The latest upstream changes (presumably #86009) made this pull request unmergeable. Please resolve the merge conflicts. |
f939d70
to
a3d6905
Compare
… force_warn level
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks!
I don't feel comfortable merging as I am not on the compiler team. Maybe @estebank or someone else could take a quick look?
(since this is edition related, and he's been looking at a lot of these) |
@bors r+ |
📌 Commit 5af5a6d has been approved by |
☀️ Test successful - checks-actions |
Unignore fix_edition_2021. The issue has been fixed by rust-lang/rust#86572.
Fixes an issue mentioned in #85512 with --cap-lints overriding --force-warnings.
Fixes #86751
r? @ehuss