-
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
What are the 'rust-analyzer diagnostics'? #6214
Comments
In this case it is |
What are the false positives by the way? What code gives them? |
Oh, i managed to post this to the wrong repo. I though i sent it posted it to https://github.com/fannheyward/coc-rust-analyzer ops. It is their readme that i refer to. |
We should document our diagnostics (we could probably auto-generate this like we do for assists). |
This is the right repo for this kind of configuration questions. It is rust-analyzer that implements them. coc-rust-analyzer just forwards them. You need to put {
"rust-analyzer.diagnostics.disabled": ["missing-unsafe"]
} in |
There's already a bug for the false positives, #5412. |
This would make |
Yes, this is the same false positive. And yes, there should be a list of these diagnostics somewhere |
Is this also available somewhere on the website? Haven't found an obvious entry in the user manual TOC. |
It should be included in the manual with the next release. |
From the readme:
I would like to disable the "This operation is unsafe and requires an unsafe block" error diagnostic, since it gives false positives with wasm-bindgen. But I have no idea what to write in that array...
The text was updated successfully, but these errors were encountered: