hashes: Remove mention of HashEngine::BYTES
What changed, and why it matters
This commit is a documentation-only cleanup. It removes a stale reference in a code comment to a type parameter (`HashEngine::BYTES`) that had already been removed from the code. No executable code was changed, and there is no security impact.
No action required. This is a non-functional documentation fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies a doc comment inside hashes/src/internal_macros.rs. The comment previously stated that a HashEngine must implement crate::HashEngine<Hash = Hash, Bytes = [u8; $len]>. Since the Bytes associated type was already removed from the trait, the comment was outdated. The patch simply deletes the Bytes = [u8; $len] part, leaving only the Default requirement. No Rust source code, trait bounds, or logic changed.
Changed components
hashes/src/internal_macros.rs (documentation comment only)Inspect captured patch +1 / −2
diff --git a/hashes/src/internal_macros.rs b/hashes/src/internal_macros.rs
index 2198e8a2..f77eb36b 100644
--- a/hashes/src/internal_macros.rs
+++ b/hashes/src/internal_macros.rs
@@ -61,8 +61,7 @@ pub(crate) use hash_trait_impls;
///
/// Restrictions on usage:
///
-/// * Requires a `HashEngine` type in this module implementing `Default`
-/// and `crate::HashEngine<Hash = Hash, Bytes = [u8; $len]>`.
+/// * Requires a `HashEngine` type in this module implementing `Default`.
macro_rules! general_hash_type {
(
$(#[$type_attrs:meta])*
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.