Cancelling async Rust ꞏ sunshowers
Correctness in the face of cancellations: a written version of my talk at RustConf 2025.| Cancelling async Rust
Correctness in the face of cancellations: a written version of my talk at RustConf 2025.| Cancelling async Rust
Sends values to the associated `Receiver`.| docs.rs
Invokes a closure, capturing the cause of an unwinding panic if one occurs.| doc.rust-lang.org
Why nextest runs each test in its own process: a game-theoretic view.| Why nextest is process-per-test
Types that pin data to a location in memory.| doc.rust-lang.org
An introduction to signals: a written version of my talk at RustConf 2023.| Beyond Ctrl-C: The dark corners of Unix signal handling
One problem with the design of async Rust is what do about async clean-up code. Consider that you| without.boats
A future represents an asynchronous computation obtained by use of `async`.| doc.rust-lang.org
An asynchronous `Mutex`-like type.| docs.rs
How my open source test runner uses async Rust.| How (and why) nextest uses tokio
Waits on multiple concurrent branches, returning when the first branch completes, cancelling the remaining branches.| docs.rs
A trait for objects which are byte-oriented sinks.| doc.rust-lang.org
