|
You are here |
blog.dureuill.net | ||
| | | | |
brokenco.de
|
|
| | | | | a moderately technical blog | |
| | | | |
mattkeeter.com
|
|
| | | | | [AI summary] The post explains how panics can occur in Rust applications using the Tokio runtime due to tasks being dropped in an arbitrary order during shutdown. | |
| | | | |
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. | |
| | | | |
github.com
|
|
| | | Marginalia. Contribute to peterkeen/marginalia development by creating an account on GitHub. | ||