Since performing blocking I O on a `CommonPool` is potential kotlinlang #coroutines

Since performing blocking I/O on a `CommonPool` is...

gregd

12/14/2017, 10:54 AM

Since performing blocking I/O on a

CommonPool

is potentially “dangerous”, maybe it would be a good idea to include a standard pool for I/O operations in

kotlinx.coroutines

? Something like RX’s

<http://Schedulers.io|Schedulers.io>()