bitcoin: Put inline types above no_inline types
What changed, and why it matters
This commit simply reorders two lines of Rust documentation import attributes. It moves an error type re-export to appear after inline type re-exports, with no functional code change. There is no security relevance.
No action required. This is a non-functional documentation/organizational cleanup.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change in bitcoin/src/blockdata/block.rs reorders pub use statements so that #[doc(inline)] re-exports precede #[doc(no_inline)] re-exports. The exact same symbols are re-exported with the same attributes; only their source order is changed. This affects generated documentation layout only and has no runtime or API impact.
Changed components
bitcoin/src/blockdata/block.rsInspect captured patch +2 / −2
diff --git a/bitcoin/src/blockdata/block.rs b/bitcoin/src/blockdata/block.rs
index bc37dbf6..cf7f0bbe 100644
--- a/bitcoin/src/blockdata/block.rs
+++ b/bitcoin/src/blockdata/block.rs
@@ -30,10 +30,10 @@ pub use primitives::block::{
};
#[doc(no_inline)]
pub use primitives::block::{InvalidBlockError, ParseHeaderError};
-#[doc(no_inline)]
-pub use units::block::TooBigForRelativeHeightError;
#[doc(inline)]
pub use units::block::{BlockHeight, BlockHeightInterval, BlockMtp, BlockMtpInterval};
+#[doc(no_inline)]
+pub use units::block::TooBigForRelativeHeightError;
#[deprecated(since = "TBD", note = "use `BlockHeightInterval` instead")]
#[doc(hidden)]
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.