Comment by dundarious
Comment by dundarious a day ago
It's hardly "all-in" if it is merely one choice of many, and the choice is made in the executable not in the library code.
Comment by dundarious a day ago
It's hardly "all-in" if it is merely one choice of many, and the choice is made in the executable not in the library code.
What does "favored" mean if event loop and direct blocking are relatively trivial and provided also/ If I can trivially use them, what do I care what Andrew or someone in core thinks? The control is all mine, and near zero cost (potential vtable indirection).
And would Rust be "all-in" if tokio was in std, so you could use its tasks everywhere? That would be a very similar level of "all-in" to Zig's current plan, but with a seemingly better API.
I understand the benefit of not being in std, but really not a fundamental issue, IMO.
In the 2026 roadmap talk Andrew Kelley spoke of the fact that stackless coroutines with iouring is the end goal here (but the requires an orthogonal improvement in the compiler for inlining that data to the stack where possible).
Do you have the timestamp? I watched that video when it came out and don't remember hearing it.
I have definitely gotten the impression that green threads will be the favored implementation, from listening to core team members and hanging around the discord. Stackless coroutines don't even exist in the language currently.