/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 blog.polybdenum.com
Fixing the Next Thousand Deadlocks: Why Buffered Streams Are Broken and How To Make Them Safer | Considerations on Codecrafting
| | boats.gitlab.io
Global Executors
4.4 parsecs away

Travel
| | One of the big sources of difficulty on the async ecosystem is spawning tasks. Because there is no API in std for spawning tasks, library authors who want their library to spawn tasks have to depend on one of the multiple executors in the ecosystem to spawn a task, coupling the library to that executor in undesirable ways. Ideally, many of these library authors would not need to spawn tasks at all.
| | aturon.github.io
Zero-cost futures in Rust ยท Aaron Turon
4.7 parsecs away

Travel
| | [AI summary] This blog post introduces Rust's zero-cost futures library, which enables efficient asynchronous I/O programming by providing high-level abstractions that compile down to low-level state-machine code without runtime overhead.
| | tmandry.gitlab.io
A formulation for scoped tasks in Rust - Tyler Mandry
4.2 parsecs away

Travel
| | For just about as long as I've been working on async Rust, the topic of scoped tasks has come up. These areasync tasks that borrow from their environment, and they would come in handy in a lot of situations. Last year the standard library stabilized thread::scope which allows synchronous threads to do this. You could imagine a similar API, but with async: asyncfn fanout(data: &Vec){task::scope(|s|{// Spawn subtasks to run in parallel.
| | tokio.rs
Tutorial | Tokio - An asynchronous Rust runtime
23.1 parsecs away

Travel
| Tokio is a runtime for writing reliable asynchronous applications with Rust. It provides async I/O, networking, scheduling, timers, and more.