Skip to content
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

Feature request: Command to run check/clippy without saving #13125

Closed
Tracked by #86
martin-t opened this issue Aug 26, 2022 · 0 comments · Fixed by #13785
Closed
Tracked by #86

Feature request: Command to run check/clippy without saving #13125

martin-t opened this issue Aug 26, 2022 · 0 comments · Fixed by #13785
Labels
A-vscode vscode plugin issues C-feature Category: feature request

Comments

@martin-t
Copy link

When Rust-analyzer › Check On Save: Enable is off, there seem to be no way to trigger that functionality manually. I think there should be a command available through ctrl+shift+P (that can also be bound to a shortcut) to trigger check/clippy without saving.

Motivation:

It's necessary to save before cargo run and at that point the user wants the project built as fast as possible to test his changes. However if check/clippy get triggered by saving, then it uses half the CPU and the cargo run command ends up being slower. It could be argued check is pretty fast but clippy is much slower and additionally seems to block the build dir for a short bit.

Being able to avoid check/clippy after saving would allow users to iterate faster in situations where they have to run the project often to test changes.


Note there was a similar issue but it had a different motivation and was closed with a workaround that is not helpful for this usecase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-vscode vscode plugin issues C-feature Category: feature request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants