rust-lang / rust-lang/rust-analyzer
SCIP symbols for inherent `impl` declarations are ambiguous
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
In #18758 the plan is to only include the first SymbolInformation in this case. An alternative might be to number them (and append these numbers using Meta SCIP descriptors), but this is tricky with how static_index.rs is implemented.
Not sure how important this is, since inherent impl declarations are not really referenceable. They do show up in symbol names, though, and some consumers of SCIP might expect to be able to resolve prefixes of SCIP symbols.
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 with issue #18758 and inspect static_index.rs, focusing on how inherent impl declarations produce SCIP SymbolInformation entries. Compare the proposed first-entry behavior with numbering via Meta SCIP descriptors; done means the resulting symbols are unambiguous and consumers can resolve relevant symbol prefixes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100