-
Notifications
You must be signed in to change notification settings - Fork 3
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 #23
Comments
Probably going to wait a bit longer on this to see how the RLS/RA extension structure plays out to avoid having to change this twice |
I'd stick with the the official Rust extension, since they are very similar in terms of features. Regarding static code analysis there is also an official Rust project called Clippy. I didn't find a VSCode extension about it. Having this installed with an extension could be really beneficial.
|
RA is very much an official project; it's also known by its other name of RLS 2.0. It was originally released as a separate extension, but is ultimately (at least most likely) going to be made available as an engine within the current VSC extension. RLS itself is largely in maintenance mode and the RA is used very widely, but also want to avoid shuffling back and forth between extensions |
Thanks for poiting that out. I didn't know that, but now I'll install it and give it a try. |
Hi, +1 here for rust-analyzer. If you look at the commit history of the official Rust package, you'll see that it's not really maintained, considering how many open issues are opened at the moment (around 200), but there wasn't any commit to master for nearly a year! Now take a look at the realease cycles and commits in the rust-analyzer repo. Yes, there are A LOT more opened issues (around 900 rn), but I would still suggest to replace it now or in the near future. Personally, I find the rust-analyzer a little bit harder to setup as I've had some issues with it, but as far as the functionality goes, it's a lot better. Also, isn't it now supported by mozila as said in their's README? |
Thanks for sharing your perspective @TDiblik, but it's not really a question of activity. There's two related, but separate, considerations still underway: RA vs RLS as the LSP, and the VS Code extension(s) on the marketplace. I'd encourage those interested in more details/status to take a look at rust-lang/vscode-rust#812 (and associated linked issues, zulip threads, etc.) Obviously for the former the plan is for RA to replace RLS as the official language server at some point, but that still has some things that need to be sorted, and until then RLS is technically still the official one (even though most folks have indeed already switched to RA) The latter consideration has less clarity, but I which I believe will result in an end state that's something other than the current RA extension namespace. I'm not keen on changing the extension pack today and then having to make a similarly substantial change yet again down the road, so this is largely blocked on the resolution of upstream plans. |
Just in case anyone's tracking this, there's been good movement upstream and RA is officially joining the Rust organization as many probably saw in the recent blog posts. There's still a few final pieces being discussed, including details like the name/publisher for the new branding of the RA extension on the marketplace (and all signs are pointing to it being something different than the current two, likely rust-lang.rust-analyzer). Once that's all sorted we'll make the corresponding update here in short order |
All the upstream changes have completed and RA is now available as |
Extension Info
Value
I've not used this one yet, but is supposed to have solved some of the problems currently experienced with the RLS extension. Mostly opening this for exploratory/research, though if anyone has any experience thoughts please share!
Similar Extensions
The text was updated successfully, but these errors were encountered: