-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Enable (and fix) extra lint groups required for in-tree build #12826
Conversation
Seems reasonable, but it will probably make every open PR unmergeable (at least we don't have a lot of them right now). |
r? @Veykril |
Yeah :( That's the only "touches 260+ files" PR tracked by #12818 - the rest is nice small incremental changes, so I wanted to get it out of the way early. |
Good thing I tried my best to get most merged over the past week |
Can't believe |
Exactly :-).
I think it should have been made into a warning in 2021. |
☀️ Test successful - checks-actions |
I don't think this added any new conflicts? 🎉 |
This enables 3 lint groups that are required to build rust-analyzer as an "in-tree" (git subtree) tool in
rust-lang/rust
, and fixes all relevant diagnostics.This change is tracked in:
Maintainer impact: more warnings, should be easy enough to fix them (it's mostly looking out for "rust-2015-isms", the lint group is poorly named). If you forget some, they'll show up during a
ra=>rust
sync.