rust-lang / rust-lang/rust-analyzer

lsp-extensions idea: Debuggables

Open
#9,711 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

So, rust-analyzer already supports runnables, which gives all the runnable targets in a neat list, so I was wondering if this could also be done for all the debuggable targets. This is more useful for editors like (neo)vim. I already have this implemented in rust-tools, which basically asks for runnables and then filters out the non debuggable commands out from it. This is not an ideal implementation, but in my experience it seems to work fine (haven't done any extensive testing though!).
Here's a small demo:
Peek 2021-07-27 21-28

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 reviewing rust-analyzer's existing runnable-target support and the linked rust-tools implementation that filters runnable commands into debuggable targets. Determine the intended LSP extension behavior and how debuggable targets should be represented for editors such as Neovim; done means an agreed design and corresponding editor-facing behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
neovim, rust
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.