You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 28, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: src/doc/unstable-book/src/compiler-flags/force-warn.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
-
# `force-warns`
1
+
# `force-warn`
2
2
3
3
The tracking issue for this feature is: [#85512](https://github.com/rust-lang/rust/issues/85512).
4
4
5
5
------------------------
6
6
7
-
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)]`.
7
+
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-warn` 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)]`.
8
8
9
9
## Example
10
10
@@ -18,4 +18,4 @@ fn dead_function() {}
18
18
fn main() {}
19
19
```
20
20
21
-
We can force a warning to be produced by providing `--force-warns dead_code` to rustc.
21
+
We can force a warning to be produced by providing `--force-warn dead_code` to rustc.
0 commit comments