Menu
I have rust-analyzer extension in VSCode.
In settings I only changed Rust-analyzer › Check On Save: Command from check to clippy (this shouldn't matter).
Problem is I don't see errors when I type, only after I save.
Typed (no error):
Saved (can see error):
Can it be changed?
619
Install the rust-analyzer extension # You can find and install the rust-analyzer extension from within VS Code via the Extensions view ( Ctrl+Shift+X) and searching for 'rust-analyzer'. You should install the Release Version.
Rust-analyzer does not support real-time linting (yet?). In short, rust-analyzer essentially runs cargo check. For small projects this can be quite fast. However, as project sizes increase, this can take significantly more time, which makes it unfeasible to check in real-time.
By default, linting for Python is enabled in Visual Studio Code using Pylint, and you can enable other linters of your choice. You can easily enable and disable all linting by using the Python: Enable Linting command.
The rust-analyzer extension has basic debugging support via the Rust Analyzer: Debug command available in the Command Palette ( Ctrl+Shift+P) and the Run|Debug CodeLens in the editor. Let's debug the Hello World program, we created earlier.
Problem is I don't see errors when I type, only after I save.
Rust-analyzer does not support real-time linting (yet?).
In short, rust-analyzer essentially runs cargo check. For small projects this can be quite fast. However, as project sizes increase, this can take significantly more time, which makes it unfeasible to check in real-time.
See also issue #4185 and "Drawbacks" on the "First Release" post.
The next best thing you can do (as you already know), is to use "check on save":
"rust-analyzer.checkOnSave.enable": true
(which is enabled by default in the VSCode extension)
165
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
