Hacker News Reader

Comment by mazeltovvv | Hacker News Reader

If you’re on vscode it is probably not the moment to switch to rust analyzer. It doesn’t work that well compared to rls. It gets tripped up easily and stops working if your code has bugs. It also doesn’t format on save.

View on HN

Anecdotally/to add a counterpoint, my experience using RA over the last few weeks has been very very positive.

Mine as well.

My experience has been very different, rust-analyzer works seamlessly in my VSCode environment, even moving from the remote WSL plugin to the remote SSH plugin. I've had zero issues with it, and it feels truly magical, when I first installed it and saw what it could do (and how fast it it) I was actually blown away. I really can't overstate how great it has been.

I can't speak to your experiences obviously, but based on mine I would recommend that anyone on VSCode gives it a shot immediately.

Not sure what you're using - rust-analyzer does support format-on-save (in fact it's actually a VS Code built-in, rust-analyzer just exposes a formatter for Rust files that then gets used by the built-in format-on-save feature)

Also compared to RLS it works much better on code with errors in, at least in my experience.

This has been my experience as well. I heard that rust-analyzer had superior IDE support but that does not currently seem to be true on VSCode.

Interesting, for me it’s far better even today.

You both should file bugs!

It seems there is more than one plugin for using Rust in vscode and they don't have the same level of support LSP and RA. It could be more clear which is considered "official" from RA's point of view. Also, one of the likely candidates only gained support for RA recently, in the last couple of versions.

The plugin is itself called “rust-analyzer.”

Reply on news.ycombinator.com