hashes: Remove lint config from source file
What the developer wrote
Authored by Tobin C. Harding
hashes: Remove lint config from source file
We handle this using `cargo rbmt` and the lint config in the repo
manifest. I checked that all these were the same there as in `lib.rs`
before removing them.
What changed, and why it matters
This commit simply removes a handful of Rust compiler/clippy lint configuration lines from a source file. The same lint settings are already present in the project's central configuration, so this is a cleanup change with no effect on program behavior or security.
No action required; this is a non-functional cleanup commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch deletes six lines of #![warn(...)] and #![allow(...)] attributes from hashes/src/lib.rs. The commit message states these lints are already configured identically in the repository manifest via cargo rbmt. There is no code logic change, no API change, and no change to the effective lint rules.
Changed components
hashes/src/lib.rsInspect captured patch +0 / −6
diff --git a/hashes/src/lib.rs b/hashes/src/lib.rs
index 037f5224..2cbb610e 100644
--- a/hashes/src/lib.rs
+++ b/hashes/src/lib.rs
@@ -55,14 +55,8 @@
#![warn(missing_docs)]
#![warn(deprecated_in_future)]
#![doc(test(attr(warn(unused))))]
-// Pedantic lints that we enforce.
-#![warn(clippy::return_self_not_must_use)]
// Instead of littering the codebase for non-fuzzing and bench code just globally allow.
#![cfg_attr(hashes_fuzz, allow(dead_code, unused_imports))]
-// Exclude lints we don't think are valuable.
-#![allow(clippy::needless_question_mark)] // https://github.com/rust-bitcoin/rust-bitcoin/pull/2134
-#![allow(clippy::manual_range_contains)] // More readable than clippy's format.
-#![allow(clippy::uninlined_format_args)] // Allow `format!("{}", x)` instead of enforcing `format!("{x}")`
#[cfg(feature = "alloc")]
extern crate alloc;
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.