rust-lang / rust-lang/rust-analyzer
Unresolved tuple indices should emit `unresolvedReferences`
Open
Nobody has claimed this yet.
A-highlighting
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
struct Foo(u32);
fn foo() {
Foo(0).1;
//^ should be marked as unresolvedReference as it does not actually resolve to a field
}
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 tracing tuple-field resolution for the Foo(0).1 example and how unresolved references are emitted. Verify that the invalid tuple index is reported as an unresolvedReferences diagnostic, then run the relevant analyzer tests or add coverage for this example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100