--- Log opened Tue May 27 00:00:55 2025
10:30 -!- pablomartin [~pablomart@2800:2143:20c0:137d::4f90] has joined #bitcoin-rust
11:02 < steven> andytoshi: you here?
11:04 < steven> So about io.. I see that there are manual bitcoin::io impls for all existing std::io types. There is also a FromStd that could be used to make a blanket impl. It seems that the manual impls could be feature-gated by a no-std feature and the other one by a std feature. Given that it's already common for crates to have those two features that can't be mutually activated? 
11:04 < steven> You mention lengthy convos, so I suppose what I suggest is somehow not possible?
11:06 < steven> Not sure if `not(feature = "std")` is sufficient, but I have seen crates with an explicit `no-std` feature.
11:06 < steven> It kinda sucks that this means that bitcoin::io traits are forcibly injected in any serialization code that uses bitcoin serialization...
11:38 < steven> It seems that this is the solution: impl_bitcoin_encode!(bitcoin::OutPoint);
15:39 -!- Ademan [~Ademan@user/Ademan] has quit [Ping timeout: 245 seconds]
17:35 -!- Ademan [~Ademan@user/Ademan] has joined #bitcoin-rust
18:05 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has joined #bitcoin-rust
18:31 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has quit [Remote host closed the connection]
18:32 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has joined #bitcoin-rust
18:36 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has quit [Ping timeout: 245 seconds]
21:04 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has joined #bitcoin-rust
21:08 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has quit [Ping timeout: 248 seconds]
21:51 -!- Ademan [~Ademan@user/Ademan] has quit [Ping timeout: 276 seconds]
--- Log closed Wed May 28 00:00:56 2025