Hmm, given that we have some IO operation that mus...

# coroutines

[groostav]

Hmm, given that we have some IO operation that must be blocking, is there a common strategy to acquire a thread that its OK to block? new Thread() will of course do the trick, but I'm wondering if there's a kind of scheduler (or idiom for keeping a singleton-scheduler) that has the maxim:

runs a blocking job, if an existing thread was allocated and is not currently running a job you'll get run on that thread, else we'll new up a new thread for you