diff options
| author | Eric Huss <eric@huss.org> | 2021-07-21 10:12:30 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-07-21 10:12:30 -0700 |
| commit | 43e25751ff6f20941bef019bdb10bce32af8f178 (patch) | |
| tree | bb1f1d4339aa9d223e1c4053d8c773f00069bc07 /src/doc | |
| parent | b9e3f3d5a21a24bf91e34a649896092dbad83a38 (diff) | |
| parent | 800c5f9202ca5309bbe372bbb8f2d6f1c29e59a5 (diff) | |
| download | rust-43e25751ff6f20941bef019bdb10bce32af8f178.tar.gz rust-43e25751ff6f20941bef019bdb10bce32af8f178.zip | |
Rollup merge of #87346 - rylev:rename-force-warn, r=nikomatsakis
Rename force-warns to force-warn The renames the `--force-warns` option to `--force-warn`. This mirrors other lint options like `--warn` and `--deny` which are in the singular. r? `@nikomatsakis` cc `@ehuss` - this option is being used by Cargo. How do we make sure the transition to using the new name is as smooth as possible?
Diffstat (limited to 'src/doc')
| -rw-r--r-- | src/doc/unstable-book/src/compiler-flags/force-warn.md (renamed from src/doc/unstable-book/src/compiler-flags/force-warns.md) | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/doc/unstable-book/src/compiler-flags/force-warns.md b/src/doc/unstable-book/src/compiler-flags/force-warn.md index 0a205be096c..052de0f379e 100644 --- a/src/doc/unstable-book/src/compiler-flags/force-warns.md +++ b/src/doc/unstable-book/src/compiler-flags/force-warn.md @@ -1,10 +1,10 @@ -# `force-warns` +# `force-warn` 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)]`. +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)]`. ## Example @@ -18,4 +18,4 @@ fn dead_function() {} fn main() {} ``` -We can force a warning to be produced by providing `--force-warns dead_code` to rustc. +We can force a warning to be produced by providing `--force-warn dead_code` to rustc. |