Support to green threads

hmspider commented 5 years ago

in https://bugs.ruby-lang.org/issues/14739 you say:

The coroutine implementation was specifically designed to handle cross-thread migrations, in the sense that all the required state to yield/resume is passed as arguments/returns to/from the coroutine.

I wonder if you intend to provide support for couroutine auto-scheduling, in the lines of:

coroutine blocks itself (userspace) -> schedule another sleeping couroutine in the same OS thread
couroutine blocks underlying thread (syscalls etc) -> schedule another sleeping couroutine in other OS thread

ioquatix commented 5 years ago

You mean in this C++ implementation?

hmspider commented 5 years ago

Assuming this is the one that was used for ruby Fiber implementation, yes.

On Fri, 11 Jan 2019 at 20:06, Samuel Williams notifications@github.com wrote:

You mean in this C++ implementation?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kurocha/coroutine/issues/2#issuecomment-453641443, or mute the thread https://github.com/notifications/unsubscribe-auth/AAiVqrWPg-BAZOD78LjufmeX7a62EVmeks5vCO7fgaJpZM4Z72s- .

kurocha / coroutine

Support to green threads #2