-
Notifications
You must be signed in to change notification settings - Fork 629
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
Revisit Clippy whitelisting #442
Comments
fix: `clippy::perf`, `clippy::correctness` (#442) The following command now returns without error: ``` cargo clippy --workspace -- -Aclippy::all -Dclippy::perf -Dclippy::correctness ``` The lints which have been corrected are: clippy::redundant_clone clippy::useless_vec clippy::trivially_copy_pass_by_ref clippy::expect_fun_call clippy::inefficient_to_string clippy::or_fun_call clippy::map_entry clippy::absurd_extreme_comparisons clippy::clone_double_ref clippy::single_char_pattern clippy::large_enum_variant
I assigned L1 implying that initial items should not be huge and Clippy + Rust compiler should guide us through, but if a bigger refactoring is necessary, we should decouple those into separate dedicated issues. |
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. |
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. |
While I am not a huge fan of clippy, for a big project with many developers, like Though, in terms of "keeping the code base sane", I don't think that's the most impactful thing. I'd say we should fix #4490 and improve compile times (by auditing our deps in Cargo.lock and cutting the cruft out) first. |
i definitely seen bugs being caught by clippy in CI, so I'm in favour of adding some of the clippy lints to at least CI. |
I'm a big favor of |
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. |
Closing in favour of #8145 |
We should start enabling [clippy](https://github.com/rust-lang/rust-clippy) gradually. To do that, we should first figure out which rules trigger warnings and document them. The purpose of this issue is to get a list of clippy rules that we do not follow now so that we can fix them in the future.
The text was updated successfully, but these errors were encountered: