rust-lang / rust-lang/rust-analyzer
Disable inlay hints when bounds are not satisfied for syntactic sugar
Open
Nobody has claimed this yet.
A-inlay-hints
A-ty
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Example:
struct A;
let a = A?;
I would personally think inlay hints should be disabled for this type of erroneous code, it gets complex when one confuses .await? with ?.await:
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
Use the reported struct A; let a = A?; and .await? versus ?.await examples to reproduce the incorrect inlay hints. Locate the inlay-hint handling for syntactic sugar and inspect how bounds errors are represented; done means hints are suppressed when those bounds are unsatisfied without changing valid-code hints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100