rust-lang / rust-lang/rust

Tracking Issue for `#[diagnostic::opaque]`

Open
#158,813 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-attributes A-diagnostics C-tracking-issue T-compiler T-lang
Dominant language
Rust
Stars
119k
Forks
16.2k
PR merge metrics
PR metrics pending

Description

There is no RFC as adding new diagnostic attributes doesn't require one as per RFC-3368
The feature gate for the issue is #![feature(diagnostic_opaque)].

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Steps
Unresolved Questions
  • list all the "unresolved questions" found in the RFC to ensure they are
    not forgotten.
Implementation history

Initial implementation: https://github.com/rust-lang/rust/pull/158608

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 initial implementation in rust-lang/rust#158608 and review the tracking checklist for diagnostic_opaque. The remaining work is represented by the documentation, nightly style, and stabilization items; completion means resolving those checklist entries and addressing any unresolved questions before stabilization.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.