What changed, and why it matters
This commit only adds two lines to a test file, checking that a type called Hkdf can be safely used across threads (Send/Sync). It is purely a test-coverage improvement with no changes to production code, no bug fixes, and no security-relevant behavior changes.
No action required; this is a benign test-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds assert_send::
Changed components
hashes/tests/api.rsInspect captured patch +2 / −0
diff --git a/hashes/tests/api.rs b/hashes/tests/api.rs
index ca5c91c4..a0628c3e 100644
--- a/hashes/tests/api.rs
+++ b/hashes/tests/api.rs
@@ -220,6 +220,8 @@ fn all_types_implement_send_sync() {
// Types are `Send` and `Sync` where possible (C-SEND-SYNC).
assert_send::<Hashes<Sha256>>();
assert_sync::<Hashes<Sha256>>();
+ assert_send::<Hkdf<sha256::HashEngine>>();
+ assert_sync::<Hkdf<sha256::HashEngine>>();
assert_send::<Engines>();
assert_sync::<Engines>();
assert_send::<OtherStructs>();
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.