-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Support rust-analyzer #2832
Comments
For anyone else who wants to use
Because they both use the LSP interface, it works as a drop in replacement. |
@cwndrws did you manage to also get clippy working with this setup ? |
@kamek-pf no, as far as I can tell, you can only use clippy if you use the |
@cwndrws I got it working, but with executable |
@elshize Yeah it looks like they changed the name of the binary in this commit. I have updated the snippet in my comment. |
Doesn't work for me. Does it work for you now? |
@xliiv yeah, I've been using it for a week or so now. Here's my rust-related ALE config in
If you're not seeing any effects, I suggest running |
@elshize thanks it helps, not it's running. it started working when i put this line let g:ale_rust_rls_toolchain = '' previously i had this one let g:ale_rust_rls_toolchain="stable" |
Does anyone know if it is possible to enable clippy for rust-analyzer? That option |
Fixes dense-analysis#2832 Signed-off-by: Iris Faey Hoffmeyer <hoffmeyer25@gmail.com>
There's now an RFC for Rust to officially transition from RLS to rust-analyzer: rust-lang/rfcs#2912 |
I can't seem to get rust-analyzer to lint properly on leaving insert mode. It takes about a second for an error to show up in the gutter, and then when I erase the offending line, the error doesn't disappear. It's not quite a replacement for rls because rls doesn't seem to have this problem. Any ideas? |
Add support for rust-analyzer
Name: rust-analyzer
URL: https://github.com/rust-analyzer/rust-analyzer
rust-analyzer is an experimental rust language server which is part of a rls 2.0 effort.
The text was updated successfully, but these errors were encountered: