Enabling internal lints shouldn't be dependent on `-Zunstable-options`
Open
Nobody has claimed this yet.
A-lints
C-discussion
T-compiler
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
We currently enable internal lints only if -Zunstable-options is passed:
This behavior is surprising at least, and seems wrong. Should we move this to some -Zenable-internal-lints or something?
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
Start by reading compiler/rustc_session/src/session.rs around the linked lines to understand how internal lints are currently enabled and how -Zunstable-options affects that decision. Trace the relevant option handling and determine the intended independent control for internal lints. Done means the dependency on -Zunstable-options is addressed with the project’s chosen behavior.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100