Merge rust-bitcoin/rust-bitcoin#1863: Removed only available in 1.46.0 line
6a18997e3c
Removed only available in 1.46.0 line (TATHAGATA ROY) Pull request description: Fix: #1850 Removed "*Important: only available in Rust 1.46+*" on the file transaction.rs from lines 1288 and 1407 respectively. ACKs for top commit: Kixunil: ACK6a18997e3c
apoelstra: ACK6a18997e3c
tcharding: ACK6a18997e3c
sanket1729: ACK6a18997e3c
Tree-SHA512: 1395384ffe301b628687cc6d154e191b6a4415acd33eb4209065c5bf94115c3210ea1d28f7d7186e41665b39b5bebae849c3fa5394786ce24bdcd57b765cdbd3
This commit is contained in:
commit
12dc0b013b
|
@ -1285,8 +1285,6 @@ const fn predict_weight_internal(
|
||||||
|
|
||||||
/// Predicts the weight of a to-be-constructed transaction in const context.
|
/// Predicts the weight of a to-be-constructed transaction in const context.
|
||||||
///
|
///
|
||||||
/// *Important: only available in Rust 1.46+*
|
|
||||||
///
|
|
||||||
/// This is a `const` version of [`predict_weight`] which only allows slices due to current Rust
|
/// This is a `const` version of [`predict_weight`] which only allows slices due to current Rust
|
||||||
/// limitations around `const fn`. Because of these limitations it may be less efficient than
|
/// limitations around `const fn`. Because of these limitations it may be less efficient than
|
||||||
/// `predict_weight` and thus is intended to be only used in `const` context.
|
/// `predict_weight` and thus is intended to be only used in `const` context.
|
||||||
|
@ -1404,8 +1402,6 @@ impl InputWeightPrediction {
|
||||||
|
|
||||||
/// Computes the prediction for a single input in `const` context.
|
/// Computes the prediction for a single input in `const` context.
|
||||||
///
|
///
|
||||||
/// *Important: only available in Rust 1.46+*
|
|
||||||
///
|
|
||||||
/// This is a `const` version of [`new`](Self::new) which only allows slices due to current Rust
|
/// This is a `const` version of [`new`](Self::new) which only allows slices due to current Rust
|
||||||
/// limitations around `const fn`. Because of these limitations it may be less efficient than
|
/// limitations around `const fn`. Because of these limitations it may be less efficient than
|
||||||
/// `new` and thus is intended to be only used in `const` context.
|
/// `new` and thus is intended to be only used in `const` context.
|
||||||
|
|
Loading…
Reference in New Issue