diff options
| author | Timo <30553356+y21@users.noreply.github.com> | 2025-08-14 08:29:55 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-08-14 08:29:55 +0000 |
| commit | ca194053d1a12249ad0b638256e822ae6ca275de (patch) | |
| tree | c73732b4afd5ebcb26d4082eee82d171977634b5 /tests/codegen-llvm/src-hash-algorithm | |
| parent | b3faf62b288709f76c45459bff9110bbea37694b (diff) | |
| parent | a43e386280f5fe5e49210cdb6db169d62eaa0733 (diff) | |
| download | rust-ca194053d1a12249ad0b638256e822ae6ca275de.tar.gz rust-ca194053d1a12249ad0b638256e822ae6ca275de.zip | |
Adjust `declare_interior_mutable_const` lint's category (#15454)
Per the root readme, `clippy::style` is a category with
> code that should be written in a more idiomatic way
description.
The code this lint guards from may be much worse than badly styled:
```rs
use std::sync::LazyLock;
// `const` instead of `static` causes `dbg!` to be printed 10 times
// instead of one.
const LICENSE_FILE_NAME_REGEX: LazyLock<String> = LazyLock::new(|| {
dbg!("I am a large regex initialized in a lazy lock!");
format!("Hello {}", "World".to_string())
});
fn main() {
for _ in 0..10 {
let _ = LICENSE_FILE_NAME_REGEX.split(" ");
}
}
```
In large projects, it's unfortunate but sometimes possible to see style
lints suppressed with
```toml
[workspace.lints.clippy]
style = { level = "allow", priority = -1 }
```
effectively turning off crucial checks for the code like above.
To keep them, promote this lint to `clippy::suspicious`:
> code that is most likely wrong or useless
category that has the same, `warn` default level, thus not failing on
false-positives which lead to
https://github.com/rust-lang/rust-clippy/issues/5863
---
changelog: [`declare_interior_mutable_const`]: promote lint's category
to `clippy::suspicious`
Diffstat (limited to 'tests/codegen-llvm/src-hash-algorithm')
0 files changed, 0 insertions, 0 deletions
