What changed, and why it matters
This commit only updates an automatically-generated API listing file. It records that a new test-helper trait implementation (for generating random 'relative::LockTime' values) is now part of the crate's public API surface. There is no code change, no bug fix, and no security-sensitive behavior introduced.
No action required. This is a metadata-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff updates api/units/all-features.txt, a checked-in public-API snapshot used by rustdoc or semver checks. It adds two lines showing that ‘bitcoin_units::locktime::relative::LockTime’ now implements ‘arbitrary::Arbitrary’ and exposes the corresponding ‘arbitrary’ method. This is a documentation/tracking file update reflecting an already-merged source change; the commit itself does not alter executable logic.
Changed components
api/units/all-features.txtInspect captured patch +2 / −0
diff --git a/api/units/all-features.txt b/api/units/all-features.txt
index 50fc84ca..faf2c928 100644
--- a/api/units/all-features.txt
+++ b/api/units/all-features.txt
@@ -1261,6 +1261,7 @@ impl<'a> arbitrary::Arbitrary<'a> for bitcoin_units::block::BlockMtpInterval
impl<'a> arbitrary::Arbitrary<'a> for bitcoin_units::locktime::absolute::Height
impl<'a> arbitrary::Arbitrary<'a> for bitcoin_units::locktime::absolute::LockTime
impl<'a> arbitrary::Arbitrary<'a> for bitcoin_units::locktime::absolute::MedianTimePast
+impl<'a> arbitrary::Arbitrary<'a> for bitcoin_units::locktime::relative::LockTime
impl<'a> arbitrary::Arbitrary<'a> for bitcoin_units::locktime::relative::NumberOf512Seconds
impl<'a> arbitrary::Arbitrary<'a> for bitcoin_units::locktime::relative::NumberOfBlocks
impl<'a> arbitrary::Arbitrary<'a> for bitcoin_units::result::MathOp
@@ -2246,6 +2247,7 @@ pub fn bitcoin_units::locktime::absolute::error::ParseTimeError::clone(&self) ->
pub fn bitcoin_units::locktime::absolute::error::ParseTimeError::eq(&self, other: &bitcoin_units::locktime::absolute::error::ParseTimeError) -> bool
pub fn bitcoin_units::locktime::absolute::error::ParseTimeError::fmt(&self, f: &mut core::fmt::Formatter<'_>) -> core::fmt::Result
pub fn bitcoin_units::locktime::absolute::error::ParseTimeError::source(&self) -> core::option::Option<&(dyn core::error::Error + 'static)>
+pub fn bitcoin_units::locktime::relative::LockTime::arbitrary(u: &mut arbitrary::unstructured::Unstructured<'a>) -> arbitrary::error::Result<Self>
pub fn bitcoin_units::locktime::relative::LockTime::clone(&self) -> bitcoin_units::locktime::relative::LockTime
pub fn bitcoin_units::locktime::relative::LockTime::deserialize<D>(deserializer: D) -> core::result::Result<Self, <D as serde::de::Deserializer>::Error> where D: serde::de::Deserializer<'de>
pub fn bitcoin_units::locktime::relative::LockTime::eq(&self, other: &bitcoin_units::locktime::relative::LockTime) -> bool
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.