Re:JEP proposed to target JDK 19: 425: Virtual Threads (Prev...
by gpderetta on Tuesday May 03, 2022 @09:00AM
(#31247731)
But you can do the same with threads: pin them to a single cpu/scheduler and use a non-preemptive scheduling strategy.
At some point you realize that explicit continuation passing, threads, coroutines and async/await are all the same thing, and the only thing that async/await gives you is a static bound on your suspended stack size (by enforcing suspension of a single activation frame).
At some point you realize that explicit continuation passing, threads, coroutines and async/await are all the same thing, and the only thing that async/await gives you is a static bound on your suspended stack size (by enforcing suspension of a single activation frame).