rust-lang / rust-lang/rust-analyzer
Assists tend to do a lot of work before actually being invoked
Open
Nobody has claimed this yet.
A-assists
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
To quote https://github.com/rust-lang/rust-analyzer/pull/18900#issue-2778935204:
Another large part is assist, that tend to execute a lot of code when listing them, for deciding whether they are available or not. Perhaps we could improve on this metric too.
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 pull request, especially its discussion of assist listing and availability checks. Trace how assists are listed before invocation and identify a measurable baseline; the issue does not name files, tests, or a concrete completion target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100