-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
cargo fix cmd no longer works #5358
Comments
ping @yaahc Do you have an idea, what's going on here and what we can do about this? |
My guess is that cargo fix was shelling out to clippy preview which got removed and now it needs to use RUSTC_WORKSPACE_WRAPPER instead now, I can open a PR to fix it, guess this means my PR finally merged into nightly 😅 |
Thanks! It would be great, if you could provide a fix for this. |
Okay so I just checked a little deeper and it looks like cargo-fix isn't an external subcommand anymore, its built into cargo, and I think I remember we decided that we didn't want to have mentions of clippy in cargo itself which is what this PR does rust-lang/cargo#7533, it completely removes all special case integration for clippy and adds the functionality to cargo that clippy would need to be implemented as an external subcommand. So the plan going forward is to have fix be invoked by clippy's external subcommand I'm currently working on the so yea short term @matthiaskrgr you should be able to still apply them on nightly by running RUSTC_WORKSPACE_WRAPPER=/path/to/clippy-driver cargo fix -Zunsable-options Which is essentially how the new cargo-clippy subcommand will work going forward. |
Here we go, WIP |
Closing this as it was fixed by #5363. I will add the missing help for the |
The https://github.com/rust-lang/rust-clippy#automatically-applying-clippy-suggestions states we can run
cargo fix -Z unstable-options --clippy
but this no longer works:Maybe it's related to rust-lang/cargo#7533 ?
EDIT: looks like it: rust-lang/cargo#7533 (comment)
The text was updated successfully, but these errors were encountered: