user0/rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Rollup merge of #152725 - ehuss:lint-level-cli, r=jieyouxu

Browse source 
Rework explanation of CLI lint level flags

I think the previous wording as either wrong or confusing. I would consider the CLI flags at a *lower* ranking, since source attributes are able to override the CLI flag.
This commit is contained in:
Stuart Cook 2026-02-18 17:29:48 +11:00 • committed by GitHub
commit f7d5a6467d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
src/doc/rustc/src/lints/levels.md
View file

@ -393,7 +393,7 @@ Here’s how these different lint controls interact:
warning: 1 warning emitted
```
3. [CLI level flags](#via-compiler-flag) take precedence over attributes.
3. [CLI level flags](#via-compiler-flag) override the default level of a lint. They essentially behave like crate-level attributes. Attributes within the source code take precedence over CLI flags, except for `-F`/`--forbid`, which cannot be overridden.
The order of the flags matter; flags on the right take precedence over earlier flags.