-
Notifications
You must be signed in to change notification settings - Fork 58
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
chore: apply clippy's suggetions #841
Conversation
Thats strange since we run clippy in CI! Would you be able to figure out why these werent caught and adapt the workflow so we catch these things earlier in the future? |
I think that precommit only runs clippy on changed files |
but then precommit doesn't run clippy rattler/.github/workflows/pre-commit.yaml Line 21 in 8a9fed3
|
We run clippy here:
|
yeah, that's what i realized |
i think we need to run it with |
We are because of:
|
Which version of rust are you using? We are still using 1.75.0 which is pinned through the rust-toolchain file. Are you perhaps using a higher version? |
Ah |
I assume you are not using pixi or rustup? How did you install the rust compiler? |
rustup? |
ps. https://releases.rs/ show that 1.80 is stable |
maybe it's a good idea to bump https://github.com/conda/rattler/blob/c02c9926318867fc61f25cb247588ae24263f9cb/rust-toolchain? or not setting it so it always stays at stable |
We want to pin the rust compiler version because otherwise every time a new version comes out we have a lot of clippy warnings (exactly what you ran into). Bumping it is a good idea, this is already happening in #837 |
#837 has been merged which bumps the rust toolchain to 1.80.0. This introduces a number of conflicts. Can you check if there are still missing clippy warnings? |
Yep, every thing looks good! |
I think it's sometimes helpful to use Clippy to avoid common mistakes. Unfortunately, this repo generates way too many of these.
The only one I could not figure out was
This commit is not supposed to change any behavior whatsoever.