What changed, and why it matters
This commit only adds a single space before the opening brace in two Rust macro definitions. It is a purely cosmetic code-style change with no effect on program behavior or security.
No action needed. This is a non-functional style-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies two macro_rules! declarations in consensus_encoding/src/encode/mod.rs, changing ‘encoder_newtype{’ to ‘encoder_newtype {’ and ‘encoder_newtype_exact{’ to ‘encoder_newtype_exact {}’. This is a whitespace-only formatting change; the Rust compiler parses both forms identically. No logic, API, or security properties are altered.
Changed components
consensus_encoding/src/encode/mod.rsInspect captured patch +2 / −2
diff --git a/consensus_encoding/src/encode/mod.rs b/consensus_encoding/src/encode/mod.rs
index 3e403037..4fe2e86e 100644
--- a/consensus_encoding/src/encode/mod.rs
+++ b/consensus_encoding/src/encode/mod.rs
@@ -46,7 +46,7 @@ pub trait Encoder {
/// Implements a newtype around an encoder which implements the
/// [`Encoder`] trait by forwarding to the wrapped encoder.
#[macro_export]
-macro_rules! encoder_newtype{
+macro_rules! encoder_newtype {
(
$(#[$($struct_attr:tt)*])*
$vis:vis struct $name:ident<$lt:lifetime>($encoder:ty);
@@ -75,7 +75,7 @@ macro_rules! encoder_newtype{
/// implements the [`Encoder`] and [`ExactSizeEncoder`] traits
/// by forwarding to the wrapped encoder.
#[macro_export]
-macro_rules! encoder_newtype_exact{
+macro_rules! encoder_newtype_exact {
(
$(#[$($struct_attr:tt)*])*
$vis:vis struct $name:ident<$lt:lifetime>($encoder:ty);
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.