Add Rust Analyzer in the install instructions

[CGMossa]

UPDATE: This PR now specifies the dependence on Rust Analyzer through the install instructions.

Currently, installing the extension for developers, depends on Rust Analyzer.
That is due to "type": "cargo" is a construction from rust-analyzer.

Instead, this just invokes cargo as a shell command.

[nvarner]

Is this a common problem? My understanding is that effectively all Rust developers on VS Code use rust-analyzer.

[CGMossa]

Either this change or the install instructions should contain rust analyzer.
A user was having issues.. They are still having them but I solved this one.

[nvarner]

Recommending installing rust-analyzer would be better, since Rust development without it would be difficult.

As an aside, do you have a link to where someone was having trouble? I don't think I saw it, but I'll offer help if I'm able, and seeing what's hard can drive development.

[CGMossa]

I'll make that PR later. https://discord.com/channels/1054443721975922748/1089255512228499516/1089415250740260915

…

On Sun, 26 Mar 2023, 08.37 Nathan Varner, ***@***.***> wrote: Recommending installing rust-analyzer would be better, since Rust development without it would be difficult. As an aside, do you have a link to where someone was having trouble? I don't think I saw it, but I'll offer help if I'm able, and seeing what's hard can drive development. — Reply to this email directly, view it on GitHub <#27 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIDVSFW4SWG64RALCDX4HLW57P3LANCNFSM6AAAAAAWHWJOXE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[CGMossa]

What's the benefit of having the cargo build task depend on rust analyzer rather than this?

[nvarner]

Oh, I see; it's not possible to even run the extension without the RA plugin.

However, using it gives us problem matchers. In general, it should usually provide better editor integration than a command. It probably also works better in strange environments. For instance, I can see someone alias an unusual command to cargo, or leave it out of their path, or something else unexpected. The RA task should still work, but the command line would not.

I think it's still best to pivot this PR into recommending installing RA. It would also be okay if there's an easy way to add the RA problem matcher to the command line task without depending on RA, and the task is renamed to indicate that it's part of the build process for testing the extension, not a recommended way of building the LSP.

[nvarner]

And thanks for providing support!

[CGMossa]

Thanks! And no problem.. Unfortunately collaboration requires that someone gets educated sometimes.

[CGMossa]

@nvarner It should be ready now.

[jakobhellermann]

You can also add rust-analyzer to vscode extension recommendations, that way it will show a little popup asking you to install rust-analyzer when you first open the project https://tattoocoder.com/recommending-vscode-extensions-within-your-open-source-projects/

[CGMossa]

Perfect suggestion; I've added it now.

[nvarner]

Thanks! This will help new users.