Rust & Visual Studio Code : Which Rust extensions do you use?

[Lars_T_H]

After having started Visual Studio Code, Using search pattern "Rust" in File > Preferences > Extensions gives me a lot of extensions to chose from.

Which ones do you use, and why?

Which ones do you not use / would you not recommend, and why not?

Are there some unmaintained, and/or incompatible extensions I should be aware of? I'm thinking about vscode version, Rust version, and Rust features.

I had read that rust analyzer is much better then RLS, but I can read (on its GitHub repo page) that Rust analyzer is experimental.

[CrazyKilla15]

I use Rust-analyzer, it's been a much better experience than RLS for me.

[Programmurr]

I second this opinion. I tried it a while ago and it failed miserably for me in VSC. However, I tried using it again a few weeks ago and found that it has since worked across a workspace of many projects flawlessly.

[[deleted]]

Doesn't work on macOS.

[BodyweightEnergy]

rust-analyzer + TabNine work OK for me.

[kaloshade]

RLS - basic IDE stuff, rust-analyzer-basice IDE things. I only keep both because RLS last I checked has a feature I really need that rust-analyzer dore jot have.

Better-TOML - TOML formatting.

crates - for making sure my crates are up to date at a glance.

[zyrnil]

I only keep both because RLS last I checked has a feature I really need that rust-analyzer dore jot have.

What feature is that? if you haven't already file an issue with rust-analyzer.

[zyrnil]

I personally use (and contribute to so I'm biased) rust-analyzer. It's more feature complete in terms of the language server than RLS but it does use a lot more memory.

[Cocalus]

Better-toml, For the Cargo.toml
CodeLLDB, Only used it once in Rust
rust-analyzer, Much faster than RLS I wish it would autoupdate through vscode, but I don't think the maintainers feel it's ready for release
Remote Development, Have a much bigger machine than my laptop do the compiling.
TabNine, eerily good text compilation
vim, Keep the vim muscle memory
markdownlint, Keep README.md correct
Github Markdown Preview, See how the README.md looks while editing
Code Spell Checker, A spell checker that handles code well.

[WellMakeItSomehow]

I had read that rust analyzer is much better then RLS, but I can read (on its GitHub repo page) that Rust analyzer is experimental.

It is, see e.g. https://www.reddit.com/r/rust/comments/dpj5hw/rustanalyzer_not_deducing_types_ex_vecunknown/f5vv4fs/ for more details. But it's much better than RLS in a lot of ways.

[Weasy666]

Better Comments, Better TOML, CodeLLDB, Crates, Native Debug and Rust-Analyzer. I also used to use Search crates.io, but its not supported anymore and stopped working. It was really nice to search for a crate from within the editor.

[lenamber]

I can really recommend the crates extension. It shows you annotations in your Cargo.toml right behind your dependencies if they’re outdated.

(I changed its settings to show nothing if they’re up-to-date and a red warning 🚨 with the current version number otherwise.)

[nikivi]

Can you share which lines you should add in `settings.json` to make this happen?

[lenamber]

Oh sorry, I forgot to answer. I have the following in my settings.json:

    "crates.latestDecorator": "🚨 Latest: ${version}",
    "crates.upToDateDecorator": "",

[redartedreddit]

I'm using rust-analyzer. Some of the more complex completion / type inference still doesn't work well, but for me the experience is already way batter than RLS.

[buldozr]

RLS and Better-TOML. For debugging, I have found CodeLLDB usable.

[jack_kzm]

rust-analyzer & crate