Andrew Poelstra 6c94546360 Merge rust-bitcoin/rust-bitcoin#2248: Implement ArbitaryOrd for absolute::LockTime ... 518f0970c9 Implement ArbitaryOrd for absolute::LockTime (Tobin C. Harding) Pull request description: At times we would like to provide types that do not implement `PartialOrd` and `Ord` because it does not make sense. I.e we do not want users writing `a < b`. This could range from kind-of-iffy to down-right-buggy (like comparing absolute locktimes). However this decision effects downstream users who may not care about what the ordering means they just need to use it for some other reason e.g., to use as part of a key for a `BTreeMap` (as we do in `miniscript` requiring the `AbsLockTime` type). A solution to this problem is to provide a wrapper data type that adds `PartialOrd` and `Ord` implementations. I wrote the `ordered` crate is for this very purpose. ACKs for top commit: apoelstra: ACK 518f0970c9 Kixunil: ACK 518f0970c9 Tree-SHA512: 05c753e650b6e2f181caf7dc363c4f8ec89237b42883bd695a64da0661436c9a7e715347f8fcf4fb19ce069cbf75a93032052e946f05fd8029f61860cf9c6225		2024-01-15 16:03:10 +00:00
..
contrib	bitcoin: Add DO_FEATURE_MATRIX	2023-12-06 10:09:05 +11:00
embedded	Implement `CompressedPublicKey`	2023-12-12 15:16:16 +01:00
examples	Improve Signature field names	2024-01-15 10:26:40 +11:00
src	Merge rust-bitcoin/rust-bitcoin#2248: Implement ArbitaryOrd for absolute::LockTime	2024-01-15 16:03:10 +00:00
tests	Improve Signature field names	2024-01-15 10:26:40 +11:00
CHANGELOG.md	Remove no-std feature	2023-12-06 09:54:33 +11:00
Cargo.toml	Implement ArbitaryOrd for absolute::LockTime	2024-01-09 13:15:29 +11:00
build.rs	Bump MSRV to Rust version 1.56.1	2023-11-23 06:20:02 +11:00