diff options
| author | bors <bors@rust-lang.org> | 2024-08-20 10:20:00 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-08-20 10:20:00 +0000 |
| commit | 2c0f3189917c80eca03e830f7a64c0fb7db6c659 (patch) | |
| tree | d413c8981d4da854300cd04ea12d700d6ba56c0c | |
| parent | d0e637da19881c335b9c14ccbbfc1f0b628fd933 (diff) | |
| parent | fc8a025f171a4cf8e5839c2bd5fa33c25357e2a0 (diff) | |
| download | rust-2c0f3189917c80eca03e830f7a64c0fb7db6c659.tar.gz rust-2c0f3189917c80eca03e830f7a64c0fb7db6c659.zip | |
Auto merge of #13289 - mrnossiom:master, r=y21
fix typo in cfg_not_test lint description Found this typo while looking at Clippy lints changelog: none
| -rw-r--r-- | clippy_lints/src/cfg_not_test.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/clippy_lints/src/cfg_not_test.rs b/clippy_lints/src/cfg_not_test.rs index b54f392bf2f..d820c1e0720 100644 --- a/clippy_lints/src/cfg_not_test.rs +++ b/clippy_lints/src/cfg_not_test.rs @@ -5,7 +5,7 @@ use rustc_session::declare_lint_pass; declare_clippy_lint! { /// ### What it does - /// Checks for usage of `cfg` that excludes code from `test` builds. (i.e., `#{cfg(not(test))]`) + /// Checks for usage of `cfg` that excludes code from `test` builds. (i.e., `#[cfg(not(test))]`) /// /// ### Why is this bad? /// This may give the false impression that a codebase has 100% coverage, yet actually has untested code. |