Document that `rustup component add rust-analyzer` just works?

[amosnier]

Quite a positive request I suppose, but although the official documentation does not seem to say that (or am I bad at searching?), it would seem like

rustup component add rust-analyzer

after a fresh install just works. Maybe it would be worth clearly documenting it, instead of letting people wonder which package they should download or whether they should build from source.

[lnicola]

It's already documented in the manual. But I suggest avoiding it, since you'll get a version that's months old and doesn't get any bug fixes.

In addition, most people will probably use the Code extension, which comes with a compatible server.

[amosnier]

I see. Thanks. Not using Code myself. I'll download the latest release then. Closing.

[amosnier]

Sorry, but I'm not sure @lnicola's recommendation was the best approach after all. With the current official Rust distribution release, I get a non-working rust-analyzer binary under .cargo/bin from the fresh installation. The fact that it does not work is in fact not an issue in itself, it is basically by design: it will work as soon as I run rustup component add rust-analyzer. However, if I do a manual installation of rust-analyzer, for instance under . local/bin as recommended, that will typically not work, because .cargo/bin really insists on being first in my PATH.

For now, I will just use the rustup version of clang-analyzer , which seems to be in line with the toolchain, i.e. at the time of writing one month-old.

I reopen, since since I guess some other users might run into the same issue. Maybe some clarifications would be useful.

[lnicola]

However, if I do a manual installation of rust-analyzer, for instance under . local/bin as recommended, that will typically not work, because .cargo/bin really insists on being first in my PATH.

We should document this issue, but the user will have to set up PATH correctly. We can't do anything about this, except maybe asking the rustup team to change the behavior of the shim, which I doubt they'll be open to.

For now, I will just use the rustup version of clang-analyzer , which seems to be in line with the toolchain, i.e. at the time of writing one month-old.

It's from the 20th of March, and currently can't be updated.

[lnicola]

@emadbaqeri which issue did you have? The version in rustup is once again very old and I don't recommend using it.

[emadbaqeri]

@emadbaqeri which issue did you have? The version in rustup is once again very old and I don't recommend using it.

I should have commented this in an other page, I do have lots of tabs open :)