rust-lang / rust-lang/rust-analyzer
Mark diagnostics originating from macro files as such
Open
Nobody has claimed this yet.
A-diagnostics
C-enhancement
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Right now, our own diagnostics coming from macro expansions can be rather confusing (mainly for derive macros, as the annotated ADT is input where we can already point, once we rework our tokenmap this will become more severe). We should note that the diagnostics stem from macro expansions.
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
The issue names no files or tests. Start by tracing how rust-analyzer creates diagnostics for macro expansions, especially derive macros, and determine where their origin can be identified. Done means diagnostics originating from macro expansions are clearly marked without changing diagnostics from other sources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100