3 ms·
Curious, since I haven't been following closely - is Tokio fit for both IO and CPU-bound work, or do you need to break into threads? I use Golang daily, and ha
by breerly 9y ago
Curious, since I haven't been following closely - is Tokio fit for both IO and CPU-bound work, or do you need to break into threads?
I use Golang daily, and have been spoiled by the opinionated approach taken to solving both CPU and IO-bound workloads.
- steveklabnik 9y agoIn one sense, IO, and in another sense, both; that is, what you do there is use futures-cpupool, which is a threadpool with a futures interface. So it still all composes just fine.