|
You are here |
blog.polybdenum.com | ||
| | | | |
without.boats
|
|
| | | | | ||
| | | | |
boats.gitlab.io
|
|
| | | | | 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. | |
| | | | |
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. | |
| | | | |
felix.plesoianu.ro
|
|
| | | [AI summary] The author explores the subjective nature of choosing programming languages, reviewing modern options like Zig and Vala alongside classics such as Ada and Fortran, while analyzing their distinct roles in software development. | ||