rust-lang / rust-lang/rust-analyzer
Improve implementation lens output
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
See https://ceronman.com/2024/05/28/types-and-self-documenting-code-in-rust/, we should do better here, probably requiring an lsp extension and then re-implementing the references-view extension for our custom handling, https://github.com/microsoft/vscode/blob/fca05df7d4a9ce627919af8cd9fc3a3f2e14e029/extensions/references-view/src/references
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked article and the VS Code references-view extension at extensions/references-view/src/references. Determine the required LSP extension and the scope of reimplementing references-view for custom handling; done means implementation lens output is improved as described by the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, vscode
- 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