-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
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
Metadata
Metadata
Assignees
Labels
No labels