rust-lang / rust-lang/rust

Tracking issue for MCP 1021: Implement a naming convention for lint/diagnostic-only `rustc_` attrs

Open
#160,808 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

B-MCP-approved C-tracking-issue S-tracking-unimplemented T-compiler
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

This is a tracking issue for MCP "Implement a naming convention for lint/diagnostic-only rustc_ attrs" (rust-lang/compiler-team#1021).

[!NOTE]
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.
Instead, open a dedicated issue for the specific matter, link to this tracking issue and ping the MCP author.
Alternatively, post in the Zulip stream linked from the MCP.

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
  • Implement the MCP
  • Adjust the documentation
Unresolved questions

None so far.

Implementation history

Empty so far.


@WaffleLapkin, consider @rustbot claim'ing the 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 by reading the linked compiler-team MCP 1021, since this tracking issue provides no implementation files, tests, or detailed naming rules. Determine the affected rustc attributes and implementation plan from the MCP, then update the relevant documentation if applicable and check off the tracking items when the convention is implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.