Fix a bunch of warnings across the workspace#2066
Conversation
webmaster128
left a comment
There was a problem hiding this comment.
Fixes are fine, but why isn't the CI complaining about those things? Can we make our CI stricter first such that we have those things covered in the future by default?
Not sure! My local VSCode config is latest Rust nightly + Yeah, I'll have a look at the CI config, that should be caught at least by the clippy step. |
|
Mybe not for all of them, but some of those things are so obvious, they should be cought by Rust or Clippy from 2016. I think we are missing something there on the tooling side if things ... |
|
After some googling, I think it's because we don't invoke the clippy tests with And a bunch of the warnings I fixed were only present after I updated my nightly yesterday, so a bunch of those lints are probably very new. |
|
But we always use |
|
Could you have a look at #2067 first and merge that? Then we can see what's left here coming from nightly. Seems like something related to shadowing for things that are already imported. |
2738d82 to
dd9aa5b
Compare
I tested it locally and nightly clippy detects it just fine but stable clippy doesn't find a dead code warning for some reason |
|
I'm wondering if it's just some new analysis on nightly, where it detects traits as unused if they aren't immediately used as a parameter (i.e. to bind a generic type parameter or to do dynamic dispatch). I'll have a look into the Rust compiler PRs, I guess |
|
Yep, seems like detecting the unused traits is part of rust-lang/rust#118257 |
923902b to
ad959c8
Compare
Sorry, the warnings were just annoying me so much when having the project open.