-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
rust analyzer reports only syntax error. #12503
Comments
For vscode you didn't save the file. |
is there a way to use the check without saving? I find the rust official extension in vscode can do such thing. |
Some things are already checked: I set "editor.semanticTokenColorCustomizations": {
"rules": {
"unresolvedReference": "#ff0000",
},
} for the red variable and enabled We already have #3107 as a tracking issue for live diagnostics, but it's very long-term.
The extension you're referring to is now deprecated, and has been unmaintained for a while. |

I am using latest rustc 1.61.0 and the latest rust-analyzer on macOS 12, when I open an rs file by helix-editor, it will only report syntax error as the picture shows. And if there are no syntax errors, no errors are reported. When I open the file, the red errors signs in line 2 and line 3 appear for 1 second and then disappear. See the video below172997535-ad817385-75f0-4a32-8914-26ac8312ea74.mov
.
The text was updated successfully, but these errors were encountered: