-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Run internal lints on the Clippy code base #3166
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
Conversation
Shouldn't |
We can try it, but I'm not sure if we want all the pedantic lints turned on for the whole clippy codebase. That would probably cause a lot of I'll try it later |
It produced 70 warnings. Travis warnings
Some of them can be fixed I guess, but most of them need an |
This looks nice! Since it's 70 warnings, I think it makes more sense to open a new issue for enabling |
@@ -1,3 +1,5 @@ | |||
#![feature(tool_lints)] | |||
#![allow(clippy::default_hash_types)] |
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.
@phansch in clippy_dev
the feature rustc_private
isn't activated, because no use rustc::...
is used. That means that also FxHashMap
cannot be used.
I think disabling the Lint here is better than adding the #![feature(rustc_private)]
. What's your opinion on this?
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.
Yea we can just disable the lint there. I don't think we will need any rustc::...
in clippy_dev
in the near future.
236ca7a
to
e28440d
Compare
I removed the pedantic lint group from Travis again. I think this can be merged now. |
We never ran the internal lints on the Clippy codebase in CI.
I added them to travis and fixed the upcoming error messages.
@phansch