--- Log opened Fri Aug 11 00:00:26 2023
00:21 -!- salvatoshi [~salvatosh@genymobile-2-6-86.fib.nerim.net] has joined #bitcoin-rust
02:41 -!- greypw2546002161 [~greypw254@grey.pw] has quit [Quit: I'll be back!]
02:42 -!- greypw2546002161 [~greypw254@grey.pw] has joined #bitcoin-rust
05:23 < yancy> stevenroose very cool.  Just a simple and probably common question - why the decision to use a super thin "green thread runtime" vs async await?
05:27 < yancy> re the workspace discussion earlier.  I find it confusing that it's not possible to just compile master since the seperate crates within the workspace are not in sync.  If the crates in the workspace are not being developed in lock step with each other, wouldn't it be best to have them in seperate crates like afilini mentioned.
06:23 -!- nex8192 [~nex8192@user/nex8192] has left #bitcoin-rust [Error from remote client]
06:34 -!- nex8192 [~nex8192@user/nex8192] has joined #bitcoin-rust
08:43 < stevenroose> yancy: because tokio is huge and impossible to review. Oh, I forgot to mention, one of the things I kept in mind designing this is that I would like to have optional tokio. So that for tokio users, it can run in their already-existing tokio runtime but non-tokio users don't have to pull in the huge dependency of tokio
08:47 < andytoshi> big kani changes https://model-checking.github.io/kani-verifier-blog/2023/08/03/turbocharging-rust-code-verification.html
09:27 -!- salvatoshi [~salvatosh@genymobile-2-6-86.fib.nerim.net] has quit [Ping timeout: 245 seconds]
11:09 -!- duderonomy [~duderonom@c-107-3-165-79.hsd1.ca.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
11:12 -!- duderonomy [~duderonom@c-107-3-165-79.hsd1.ca.comcast.net] has joined #bitcoin-rust
--- Log closed Sat Aug 12 00:00:27 2023