From: Matt Corallo Date: Thu, 12 Oct 2023 18:23:51 +0000 (+0000) Subject: Drop warning about mixing `no-std` and `std` `ProbabilisticScorer`s X-Git-Tag: v0.0.119~4^2~3 X-Git-Url: http://git.bitcoin.ninja/index.cgi?a=commitdiff_plain;h=81389dee306d960a8030bec5ffa304004148ce85;p=rust-lightning Drop warning about mixing `no-std` and `std` `ProbabilisticScorer`s Now that the serialization format of `no-std` and `std` `ProbabilisticScorer`s both just use `Duration` since UNIX epoch and don't care about time except when decaying, we don't need to warn users to not mix the scorers across `no-std` and `std` flags. Fixes #2539 --- diff --git a/lightning/src/routing/scoring.rs b/lightning/src/routing/scoring.rs index cf1393873..0dd0c2ea3 100644 --- a/lightning/src/routing/scoring.rs +++ b/lightning/src/routing/scoring.rs @@ -464,11 +464,6 @@ impl ReadableArgs for FixedPenaltyScorer { /// formula, but using the history of a channel rather than our latest estimates for the liquidity /// bounds. /// -/// # Note -/// -/// Mixing the `no-std` feature between serialization and deserialization results in undefined -/// behavior. -/// /// [1]: https://arxiv.org/abs/2107.05322 /// [`liquidity_penalty_multiplier_msat`]: ProbabilisticScoringFeeParameters::liquidity_penalty_multiplier_msat /// [`liquidity_penalty_amount_multiplier_msat`]: ProbabilisticScoringFeeParameters::liquidity_penalty_amount_multiplier_msat