Coroutines make using nio simpler. For blocking io they provide little benefit as they will need one thread per io channel anyway

@uli So I assumed that a coroutine blocked on (a blocking read or write) will suspend allowing other coroutines on the same thread to be dispatched. Let’s say I had one suspend coroutine doing blocking I/O and a bunch of other coroutines on the same performing some sort of compute, are you saying that the compute coroutines will not be dispatched?

@Dexter coroutines can not magically turn blocking into suspension. They can be used to turn callbacks into suspension. I.e. with the coroutines.nio package you get calls like aread and awrite. You use aread inside a coroutine just like you would use a blocking read but it will suspend instead of block until the read completes.

Got it. So just for clarification, if I made a blocking I/O call my whole thread and all associated coroutines on that thread will block on the I/O? That is assuming that my coroutines are not using a context with an underlying thread pool. I think I got this all wrong.

Exactly

Thanks Uli.