`use` `Vec` from `alloc` rather than the crate prelude
What the developer wrote
Authored by Matt Corallo
`use` `Vec` from `alloc` rather than the crate prelude
This avoids confusing the bindings generator.
What changed, and why it matters
This is a tiny code cleanup change. It swaps one way of importing the same standard `Vec` type for another, purely to help an automated bindings generator understand the code. There is no security issue here.
No security action needed. This is a routine refactor.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit changes a single use statement in lightning/src/ln/funding.rs from crate::prelude::Vec to alloc::vec::Vec. Both refer to the same standard library Vec type. The stated motivation is to avoid confusing the bindings generator. No logic, behavior, or trust boundary changes are present.
Changed components
lightning/src/ln/funding.rsInspect captured patch +2 / −1
diff --git a/lightning/src/ln/funding.rs b/lightning/src/ln/funding.rs
index ae7e36a..3cabb82 100644
--- a/lightning/src/ln/funding.rs
+++ b/lightning/src/ln/funding.rs
@@ -9,12 +9,13 @@
//! Types pertaining to funding channels.
+use alloc::vec::Vec;
+
use bitcoin::{Amount, ScriptBuf, SignedAmount, TxOut};
use bitcoin::{Script, Sequence, Transaction, Weight};
use crate::events::bump_transaction::Utxo;
use crate::ln::chan_utils::EMPTY_SCRIPT_SIG_WEIGHT;
-use crate::prelude::Vec;
use crate::sign::{P2TR_KEY_PATH_WITNESS_WEIGHT, P2WPKH_WITNESS_WEIGHT};
/// The components of a splice's funding transaction that are contributed by one party.
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.