Anonymous
10/20/2025, 5:46:42 PM
No.106950632
>>106950553
A large portion of the libraries that make up the "rust async ecosystem" can only work with tokio because they want to spam tokio::spawn for everything, just like how you can spam goroutines in go. Since the tokio runtime is hidden global state, they don't even ask for a reference or anything, they just crash at runtime with the message posted by the other anon:
>there is no reactor running, must be called from the context of a Tokio 1.x runtime.
You can use async rust by yourself and never see any of this, but if you've tried to use other people's async rust libraries, you know what I'm talking about.
A large portion of the libraries that make up the "rust async ecosystem" can only work with tokio because they want to spam tokio::spawn for everything, just like how you can spam goroutines in go. Since the tokio runtime is hidden global state, they don't even ask for a reference or anything, they just crash at runtime with the message posted by the other anon:
>there is no reactor running, must be called from the context of a Tokio 1.x runtime.
You can use async rust by yourself and never see any of this, but if you've tried to use other people's async rust libraries, you know what I'm talking about.