rust-lang / rust-lang/rust-analyzer

Ability to split find usages result based on usage in pattern and expression

Open
#14,873 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-ide A-pattern C-feature
Dominant language
Rust
Stars
16.9k
Forks
2.2k
Avg merge
1d 12h
Merged PRs (30d)
72

Description

Using a struct or enum variant in a pattern has very different meaning from in an expression. In expression its a construction, but in pattern its an inspection. I almost always know whether I look for construction or inspection, so I think either grouping the results based on this categories or adding more specific commands for querying one of them would work.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the existing find-usages entry point and determine how usages distinguish patterns from expressions. Compare the two proposed outcomes: grouping results by construction versus inspection, or adding commands that query one category. Done means users can reliably inspect either category separately.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.