Well in any event: If I do use the Async kernel32 ...
# coroutines
g
Well in any event: If I do use the Async kernel32 functions then it means I can get all callbacks centralized on one thread, which can then dispatch notifications to the various coroutine schedulers (eg
Channel
instances), getting them running on whatever thread they're comfortable with (eg a UI thread or the
CommonPool
)