-
Notifications
You must be signed in to change notification settings - Fork 0
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
Gradually add in useful clippy lints that we currently don't check for #97
Comments
Well, stratisd has about 40 warnings, and devicemapper has 0. Let's do it for devicemapper now, so we can catch as necessary. Or alternatively, let's grab one we like and do that. |
|
@jbaublitz If you find a lint in the nursery or pedantic categories that you find especially valuable, please feel free to propose it. |
The only ones that jump out at me immediately are some of the integer lints around wrapping and lossy conversions. It could be interesting to see if we guard against that everywhere. |
@jbaublitz If you want to go ahead and try one of those out in a PR go right ahead. |
I'm not sure that the suggested lints are going to help here. Most of the warnings are about |
Ok! We'll let this sit until something does come up. |
If we're just letting it sit, we can remove it from every board. |
I'm thinking of going through these lints and turning on all the ones that make obvious sense and that we already don't infringe, in order to prevent future infringements. Then we can work on the more tricky ones, that we are actually infringing and that are important to us. |
We stopped trying to keep our CLIPPY_PEDANTIC variable in the stratisd Makefile up-to-date and maintained a long time ago, because we got a really limited benefit from doing that. Maybe someday we'll remove that variable entirely and rely on clippy processes to promote the pedantic lints to more interesting categories. It is not in use for any of the other Rust projects. |
Ultimately this will be helpful. But we might have to add them in gradually. Some are hard to fathom.
The text was updated successfully, but these errors were encountered: