Document CompactTarget order/equality
Add documentation to the `CompactTarget` type explaining the nuance surrounding order/equality. Close: #2110
This commit is contained in:
parent
2e8bd5f06a
commit
c8caee2b5e
|
@ -337,6 +337,13 @@ do_impl!(Target);
|
|||
///
|
||||
/// OpenSSL's bignum (BN) type has an encoding, which is even called "compact" as in bitcoin, which
|
||||
/// is exactly this format.
|
||||
///
|
||||
/// # Note on order/equality
|
||||
///
|
||||
/// Usage of the ordering and equality traits for this type may be surprising. Converting between
|
||||
/// `CompactTarget` and `Target` is lossy *in both directions* (there are multiple `CompactTarget`
|
||||
/// values that map to the same `Target` value). Ordering and equality for this type are defined in
|
||||
/// terms of the underlying `u32`.
|
||||
#[derive(Copy, Clone, Debug, Default, PartialEq, Eq, PartialOrd, Ord, Hash)]
|
||||
#[cfg_attr(feature = "serde", derive(Serialize, Deserialize))]
|
||||
#[cfg_attr(feature = "serde", serde(crate = "actual_serde"))]
|
||||
|
|
Loading…
Reference in New Issue