--- Log opened Wed May 28 00:00:56 2025
01:00 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has joined #bitcoin-rust
01:05 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has quit [Ping timeout: 276 seconds]
01:49 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has joined #bitcoin-rust
01:53 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has quit [Ping timeout: 245 seconds]
02:17 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has joined #bitcoin-rust
02:22 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has quit [Ping timeout: 260 seconds]
03:17 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has joined #bitcoin-rust
03:22 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has quit [Ping timeout: 252 seconds]
04:18 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has joined #bitcoin-rust
04:23 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has quit [Ping timeout: 248 seconds]
06:40 < andytoshi> steven: nope, if a blanket impl was gated by a std feature this would break compilation for some users when std is turned on
06:41 < andytoshi> yes, we could put the no-std feature back... but this is still really not kosher
06:42 < andytoshi> oh, and if nostd and std were exclusive, that's definitely not allowed
06:43 < andytoshi> steven: the problem is that if somebody implements bitcoin::io directly for their type, and then something else in their dep tree turns on the `std` feature causing us to have a blanket impl of bitcoin::io for all std::io, then their manual impl will conflict
06:44 < andytoshi> this situation is probably the single most broken thing about the rust stdlib. it's caused years and years of completely unnecessary pain across most every crate in the rust-bitcoin ecosystem
06:56 -!- proofofkeags [~proofofke@2607:fb91:1a1:9ab:8e7:3ae4:501f:8941] has joined #bitcoin-rust
07:01 -!- proofofkeags [~proofofke@2607:fb91:1a1:9ab:8e7:3ae4:501f:8941] has quit [Ping timeout: 268 seconds]
07:13 < andytoshi> steven: we have "adaptor structs" FromStd and ToStd that you can manually use ... i believe the most sensible way to deal with bitcoin::io, if you don't care about nostd, is to always use these adaptor structs before dealing with the rust-bitcoin interfaces
07:14 < andytoshi> and if you _do_ care about nostd, then you should use bitcoin::io in your own code everywhere rather than std::io
07:17 -!- pablomartin [~pablomart@2800:2143:20c0:137d::4f90] has quit [Ping timeout: 276 seconds]
07:19 -!- pablomartin [~pablomart@2800:2143:20c0:137d::4f90] has joined #bitcoin-rust
07:27 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has joined #bitcoin-rust
07:45 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has quit [Remote host closed the connection]
07:45 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has joined #bitcoin-rust
07:50 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has quit [Ping timeout: 276 seconds]
10:03 -!- Ademan [~Ademan@user/Ademan] has joined #bitcoin-rust
19:37 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has joined #bitcoin-rust
19:42 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has quit [Ping timeout: 272 seconds]
21:39 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has joined #bitcoin-rust
21:43 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has quit [Ping timeout: 245 seconds]
22:36 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has joined #bitcoin-rust
22:41 -!- proofofkeags [~proofofke@wsip-24-234-111-66.lv.lv.cox.net] has quit [Ping timeout: 248 seconds]
--- Log closed Thu May 29 00:00:57 2025