Explore >> Select a destination
|
You are here 
|
without.boats | ||
| | | | |
www.ncameron.org
|
|
| | | | | Completion-model IO systems don't work naturally with the Read trait. In this post I want to explore why that is and some alternatives. Many of the issues are related to cancellation, and there is some discussion ongoing around whether we can change or amend the cancellation mechanisms in async Rust, | |
| | | | |
tmandry.gitlab.io
|
|
| | | | | 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. | |
| | | | |
sabrinajewson.org
|
|
| | | | | The main focus of this article will be on attempting to design a system to support asynchronous destructors in the Rust programming language, figuring the exact semantics of them and resolving any issues encountered along the way. By side effect, it also designs a language feature called async genericity which enables supporting blocking and asynchronous code with the same codebase, as well as designing a system for completion-guaranteed futures to be added to the language. | |
| | | | |
www.ralfj.de
|
|
| | | |||
