Closed ehiggs closed 5 years ago
If clippy runs into docstring errors then it will report those errors and bail. This might give the impression that the code is pretty sound since the only issues are docstring things. Well, that wouldn't be correct! If we fix these 36 docstring issues then a cascade of >450 errors on the actual code is the result.
This is because clippy has two passes. Early and late. If you have 'deny' set on something in an early phase (e.g. docstring stuff) then it will flag errors and bail as described. This isn't an issue with clippy or anything since users should be aware that they set clippy up to report errors when it finds them.
(noting this so when I read my old issues in 3 months I don't bother the clippy team asking if this is a clippy bug again).
As leaf is no longer maintained, this will never be fixed.
If clippy runs into docstring errors then it will report those errors and bail. This might give the impression that the code is pretty sound since the only issues are docstring things. Well, that wouldn't be correct! If we fix these 36 docstring issues then a cascade of >450 errors on the actual code is the result.
For the lints that refer to a wiki page we can use the following grep:
This is 461 errors, but there are 481 errors in all. The ones that don't refer to a page are mostly about unneeded use of
&
when calling functions and usingmatch
on boolean expressions (clippy prefersif
/else
).Obviously not all of these need to fixed in a humungous PR, but what should be done?
FWIW, here's a patch that fixes the docstring issues: docstring.patch.zip
Patch is a zip since github doesn't want any files with .patch as a suffix. 😞
NB: this required updating clippy to 0.0.67 in Cargo.toml.