Mark this repository as deprecated or update the README

[peabnuts123]

Looks like this extension was more-or-less replaced by https://github.com/rust-lang/rust-analyzer several years ago and hasn't been updated since. I understand that #812 is showing an intention to (possibly) merge rust-analyzer back in "one day", but I'm not seeing any concrete plans to do that. As of today a user new to rust (like myself) installing support into vscode sees this extension as:

• Having 1.5M (vs. 500k) downloads
• Being authored by "The Rust Programming Language" (vs. @matklad )
• Having the actual Rust logo

Which leads me to believe that most people will install this one over the other. This one seems to work ~okay (though code completion was not working very well) but I'm not sure to what extent.

This repo should probably be marked as deprecated in GitHub or, if still serving some other purpose, at least the README should be updated to point people to the other vscode extension. This will help users get the best experience and also reduce noise etc. in GitHub (I can see you still receive new issues every week or two).

[lnicola]

CC #927.

I think the current plan is to move rust-analyzer to the same Market publisher and leave RLS as a legacy option. Merging the two seems like a bad idea IMO.

[peabnuts123]

That's fair enough. I can see the 2 projects are separate and there will be significant overlap between the two. However, I still think unless this repository intends to be maintained then it should have some wording on it at least describing the situation. As highlighted in that issue #927 - there are a lot of reviews pointing out that this one doesn't seem to work any more (I assume it has likely been surpassed by the Rust version itself). Are you open to a PR? I could have a go at it (although I don't quite have the full context so would need somebody closer to the project to read over it).

[lnicola]

You can see https://blog.rust-lang.org/2022/02/21/rust-analyzer-joins-rust-org.html for more context.

Are you open to a PR? I could have a go at it

I'm just one of the rust-analyzer maintainers. I've been lurking here for a couple of years pointing users to RA when I could check that their bugs didn't reproduce there, but I don't have commit rights here (or didn't, until last week).

[valbaca]

Each Rust tutorial and beginner group I come across always has a section about "Don't use the Rust plugin, use rust-analyzer instead"

This is a broken step in the Rust beginner staircase and should be resolved.