You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 24, 2023. It is now read-only.
Right now, there are two main interfaces for running fixes:
`cargo fix [--tests|--benches|--lib]
cargo clippy --fix
It's weird that they are so different - I would expect this to be a cargo fix --clippy option. Would it be possible for rustfix to add support so we can unify the interface?
cc @rust-lang/clippy
The text was updated successfully, but these errors were encountered:
I seem to remember that we had this discussion before in the cargo repo. I think it was in the context of making the clippy subcommand a first class citizen of cargo instead of having it as an external tool that adds this subcommand (which was rejected back then, because Clippy doesn't have to be installed). Having Clippy as a first class citizen would have had the advantage that cargo could also handle things like cargo fix --clippy. But since Clippy has to register itself as a subcommand, we also had to implement the --fix flag on our own.
This is the PR were this discussion took place: rust-lang/cargo#7382 (warning: it's really long!)
Right now, there are two main interfaces for running fixes:
cargo clippy --fix
It's weird that they are so different - I would expect this to be a
cargo fix --clippy
option. Would it be possible for rustfix to add support so we can unify the interface?cc @rust-lang/clippy
The text was updated successfully, but these errors were encountered: