Search Results
6/17/2025, 4:12:07 PM
>>105619442
>I don't know how Rust handles them
Futures returned by coroutines are marked whenever they borrow anything and whenever they can be passed around to different threads, depending on how they capture the data and what kind of data do they keep between awaits. Depending on kind of runtime you choose, your tasks might be limited to 'static and/or Send/Sync traits. Eg a single-threaded runtime knows it won't have to pass futures across thread boundaries.
All of this is checked by the compiler. It does remove some obvious foot guns making it harder to make mistake, but async without GC will never be easy either way.
>I don't know how Rust handles them
Futures returned by coroutines are marked whenever they borrow anything and whenever they can be passed around to different threads, depending on how they capture the data and what kind of data do they keep between awaits. Depending on kind of runtime you choose, your tasks might be limited to 'static and/or Send/Sync traits. Eg a single-threaded runtime knows it won't have to pass futures across thread boundaries.
All of this is checked by the compiler. It does remove some obvious foot guns making it harder to make mistake, but async without GC will never be easy either way.
Page 1