rust-lang / rust-lang/rust-analyzer

Native diagnostics should support linked/related sub diagnostics

Open
#16,059 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Very rough information but we now have call and def site information for macros, so a diagnostic originating from the def site should be repoted at the call site with the def site info attached. We should be able to support this. Also needed for other non macro related things, once we track obligation causes and the like.

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 by locating the native diagnostics implementation and the existing macro call-site and definition-site information. Determine how a diagnostic from a definition site could be reported at its call site with the definition-site information attached, while accounting for future obligation causes and other related diagnostics.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers, devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.