What the developer wrote
Authored by Tobin C. Harding
units: no_inline error
As is customary here, use `no_inline` on error re-export.
What changed, and why it matters
This is a one-line documentation-only change in the Rust Bitcoin library. It adds a Rust attribute that prevents a re-exported error type from being shown as inlined in generated API documentation. There is no change to executable code, behavior, or security.
No security action needed. This is a cosmetic/documentation consistency change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit adds #[doc(no_inline)] to a pub use self::error::LockTimeDecoderError; re-export in units/src/locktime/absolute/mod.rs. This Rust doc attribute only affects how rustdoc renders the re-exported type in documentation pages; it does not alter compilation output, runtime behavior, type visibility, or any security property.
Changed components
units/src/locktime/absolute/mod.rsInspect captured patch +1 / −0
diff --git a/units/src/locktime/absolute/mod.rs b/units/src/locktime/absolute/mod.rs
index 8ef4846f..c1065839 100644
--- a/units/src/locktime/absolute/mod.rs
+++ b/units/src/locktime/absolute/mod.rs
@@ -25,6 +25,7 @@ pub use self::error::{
ConversionError, IncompatibleHeightError, IncompatibleTimeError, ParseHeightError, ParseTimeError,
};
#[cfg(feature = "encoding")]
+#[doc(no_inline)]
pub use self::error::LockTimeDecoderError;
/// The Threshold for deciding whether a lock time value is a height or a time (see [Bitcoin Core]).
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.