rust-lang / rust-lang/rust-analyzer
r-a fails to resolve associated function with complicated where bound
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
rust-analyzer version: 0.4.1183-standalone (6bea872ed 2022-08-26)
rustc version: rustc 1.65.0-nightly (878aef79d 2022-08-20)
relevant settings: N/A
Code in question:
Expected outcome: hovering over Simple::new shows its definition at
Observed outcome:
Naively, I would suspect this has to do with const generics?
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
Reproduce the hover behavior in evanescence_core/src/numerics/optimization/simple_x.rs, comparing the call at line 311 with the definition at lines 168-179. Start by investigating associated-function resolution for the complicated where bound and possible const-generic involvement; done means hovering over Simple::new resolves to its definition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100