terminated async runtime ecosystem split
uvd
👎9
👍6
😕5
All 2 comments
Please review the RFC process.
jhpratt
on 29 Apr 2020
It likely that a simple single-threaded executor will be a added to libstd at some point, but almost all production uses of async/await will still want to use their own executor tailored to the specific application's needs.
What causes the ecosystem split is not having multiple executors, but multiple reactors, so putting work into how to provide a generic reactor in libstd, or how to enable interop between them would be more useful for solving this problem.
jonas-schievink
on 2 May 2020
👍8
❤1
Was this page helpful?
0 / 5 - 0 ratings
Related issues
mahkoh
路
3Comments
3442853561
路
3Comments
silversolver1
路
3Comments
burdges
路
3Comments
mqudsi
路
3Comments
Most helpful comment
It likely that a simple single-threaded executor will be a added to libstd at some point, but almost all production uses of async/await will still want to use their own executor tailored to the specific application's needs.
What causes the ecosystem split is not having multiple executors, but multiple reactors, so putting work into how to provide a generic reactor in libstd, or how to enable interop between them would be more useful for solving this problem.