Also, why have Pool implement CoroutineScope and not Dispatcher... the`coroutineScope` builder function inherits its job anyways, and you can change the dispatcher with

launch(<http://Dispatchers.IO|Dispatchers.IO>)

from the pool... that way you can cancel the whole Dispatcher class with all the workers, you could also make it a supervisor scope if you don't want one failing subtask to cancel its parent...