← Watch feed
consensus_encoding: Add crate level doc for decode_from_hex
What changed, and why it matters
This commit is a pure documentation update. It adds one missing bullet point to the crate-level documentation list, describing a function that already existed. No code behavior changed.
Recommended action
No action required. This is a non-security documentation change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds a single line to consensus_encoding/src/lib.rs documenting the existing decode_from_hex function in the module-level doc comment. There are no code, API, or logic changes.
Changed components
consensus_encoding/src/lib.rs documentationInspect captured patch +1 / −0
diff --git a/consensus_encoding/src/lib.rs b/consensus_encoding/src/lib.rs
index 8981aa0b..cf8462a3 100644
--- a/consensus_encoding/src/lib.rs
+++ b/consensus_encoding/src/lib.rs
@@ -40,6 +40,7 @@
//! * [`decode_from_read_unbuffered_with`]: As above with custom sized stack-allocated buffer.
//! * [`decode_from_slice`]: Decode from a byte slice (errors if slice is not completely consumed).
//! * [`decode_from_slice_unbounded`]: Slice can contain additional data after decoding completes.
+//! * [`decode_from_hex`]: Decode from a hex string without heap allocations.
//!
//! Each function above takes a type parameter `T: Decode` to select the output type and its
//! associated decoder. The following variants instead accept a [`Decoder`] type directly,
Risk score
Our methodology →Why this scored 15/100
Human-validated context
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
No validated notes yet.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.