Mastodon Feed
Boosted by bcantrill ("Bryan Cantrill"):
ahl ("Adam Leventhal") wrote:
A bunch of folks at Oxide uncovered a tricky deadlock associated with async Rust (yes, another!), so--of course--@bcantrill and I got the crew together to discuss. If you're writing async Rust, you'll want to know how to avoid and diagnose "Futurelock"
https://www.youtube.com/watch?v=cqpLGvalyrI
Also:
- @ interviews to be the Blue Jays new manager
- a dramatized re-enactment of the critical moments diagnosing Futurelock
- async Rust doesn't make us mad, just disappointed