Explore >> Select a destination
|
You are here 
|
without.boats | ||
| | | | |
async.rs
|
|
| | | | | ||
| | | | |
docs.rs
|
|
| | | | | The Tokio runtime. | |
| | | | |
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. | |
| | | | |
til.simonwillison.net
|
|
| | | A popular nightmare scenario for AI is giving it access to tools, so it can make API calls and execute its own code and generally break free of the constraints of its initial environment. | ||
