What the developer wrote
Authored by phrwlk
chore: fix path to the wrapper
What changed, and why it matters
This is a trivial documentation-only change in an example file. It updates two comments to reflect the correct module path for a wrapper type (`bitcoin_io::FromStd` instead of `bitcoin_io::bridge::FromStd`). No executable code was changed, and there is no security relevance.
No action required. This is a non-security documentation fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies only comments in bitcoin/examples/io.rs. It corrects outdated references to bitcoin_io::bridge::FromStd and io::bridge::FromStd to bitcoin_io::FromStd and io::FromStd respectively. No logic, imports, APIs, or behavior changed.
Changed components
bitcoin/examples/io.rs (comments only)Inspect captured patch +2 / −2
diff --git a/bitcoin/examples/io.rs b/bitcoin/examples/io.rs
index 82ca0cb0..1cabb4f4 100644
--- a/bitcoin/examples/io.rs
+++ b/bitcoin/examples/io.rs
@@ -17,7 +17,7 @@ fn main() {
// Encode to a custom type by implementing `bitcoin_io` traits.
encode_to_custom_type();
- // Encode to a foreign custom type by using the `bitcoin_io::bridge::FromStd` wrapper.
+ // Encode to a foreign custom type by using the `bitcoin_io::FromStd` wrapper.
encode_using_wrapper();
}
@@ -75,7 +75,7 @@ fn encode_to_custom_type() {
/// Encodes to a custom type by using the `bitcoin_io::bridge` module.
///
/// If you have a type that you don't control that implements `std::io::Write` you can still encode
-/// to it by way of the `io::bridge::FromStd` wrapper.
+/// to it by way of the `io::FromStd` wrapper.
fn encode_using_wrapper() {
use pretend_this_is_some_other_crate::WriteCounter;
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.