feat(lsp): target architecture switching command for RustAnalyzer

[borngraced]

target_switch3.mp4

By default, RustAnalyzer uses the system architecture when analyzing and building projects. However, we often need to work with alternative targets, such as WebAssembly (wasm32-unknown-unknown). Without the ability to switch targets easily, we must manually reconfigure our rust-analyzer.config.target which can be inefficient.

Changes Made

• Added the :rustanalyzer target <target_arch> command:
• Accepts a valid rustc target (e.g., wasm32-unknown-unknown).
• Defaults to the system architecture if no target is provided.
• Notifies the user if an invalid target is supplied.
• Modified the restart_impl function to incorporate the new logic for setting and validating target architectures.

ref: https://doc.rust-lang.org/rustc/targets/built-in.html

[github-actions]

Review Checklist

Does this PR follow the Contribution Guidelines? Following is a partial checklist:

Proper conventional commit scoping:

• For example, fix(lsp): some lsp-related bugfix

• Pull request title has the appropriate conventional commit prefix.

If applicable:

• Tested
  • Tests have been added.
  • Tested manually (Steps to reproduce in PR description).
• Updated documentation.

[mrcjkb]

Thanks, this looks great 🙏 😄

[mrcjkb]

suggestion: vim.system():wait() blocks Neovim's event loop.
It's generally better to use vim.system and pass in a callback, which is a function(result) where result is a vim.SystemCompleted.

This means that this function has to be changed, e.g. to with_rustc_targets(callback: fun(targets)).
It's a bit of a refactor, but I think it's doable.

[borngraced]

done

[borngraced]

@mrcjkb I worked on the improvement fixes.