nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2025-05-14 02:49:40 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add a page on force-warns in unstable book

Browse Source
This commit is contained in:
Ryan Levick 2021-06-02 18:07:39 +02:00
parent dc2db73899
commit ab419314e9
2 changed files with 22 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
compiler/rustc_middle/src/lint.rs
View File

@ -365,7 +365,7 @@ pub fn struct_lint_level<'s, 'd>(
sess.diag_note_once(
&mut err,
DiagnosticMessageId::from(lint),
"Warning forced by `force-warns` commandline option",
"warning forced by `force-warns` commandline option",
);
}
}

21
src/doc/unstable-book/src/compiler-flags/force-warns.md Normal file
View File

@ -0,0 +1,21 @@
# `force-warns`
The tracking issue for this feature is: [#85512](https://github.com/rust-lang/rust/issues/85512).
------------------------
This feature allows you to cause any lint to produce a warning even if the lint has a different level by default or another level is set somewhere else. For instance, the `force-warns` option can be used to make a lint (e.g., `dead_code`) produce a warning even if that lint is allowed in code with `#![allow(dead_code)]`.
## Example
```rust,ignore (partial-example)
#![allow(dead_code)]
fn dead_function() {}
// This would normally not produce a warning even though the
// function is not used, because dead code is being allowed
fn main() {}
```
We can force a warning to be produced by providing `--force-warns dead_code` to rustc.