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
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.
The text was updated successfully, but these errors were encountered:
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 thecargo 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.
The text was updated successfully, but these errors were encountered: