rust-lang / rust-lang/rust-analyzer

TCP support

Open
#14,473 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-feature
Dominant language
Rust
Stars
16.9k
Forks
2.2k
Avg merge
1d 12h
Merged PRs (30d)
72

Description

Rust analyzer is pretty heavyweight, so I'd like to run a persistent copy that neovim can use without the startup/teardown cycle each time I jump into an editor.

Ideally multiple instances of an IDE should be able to use the same LSP as well, further reducing redundant work.

I haven't found any issue even mentioning this, so opening this feature request for it.

ra-multiplex is worth mentioning as relevant; it can proxy the current stdio interface into TCP ports, but not without another layer of complexity in between.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the issue description and the linked ra-multiplex project to understand how it proxies the current stdio interface into TCP ports. Determine the design needed for a persistent Rust-analyzer instance that multiple IDE instances can share. Done means Rust-analyzer supports TCP-based use without an external proxy layer.

Written by the indexing model from the issue text.

Assessment

Tech stack
neovim, rust
Domain
devtools, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.