Taking a CpuPool about futures-rs HOT 4 CLOSED

Maybe an implicit threadpool stored in TLS, then primitives that access it?

Passing a threadpool around would get cumbersome if you had to funnel it through all the futures. You could store it with any number of things, but a simple "go do this closure over there" seems useful to me. Are there many cases in which you would want more threads than CPUs? Because if not, the thread pool could also implicitly construct itself.

from futures-rs.

There's a little bit of this being fleshed out in #95, but I think in general this is going to require some form of threading around a CpuPool to spawn work on if you want to spawn work onto a thread pool.

from futures-rs.

OK, if you don't think there's a use-case for a trait, I will just have the user pass in a CpuPool in my library for now. I will save you a lecture about the dependency inversion principle :)

from futures-rs.

@bluetech oh I'm not saying that there's no use for this, I just wanted to give an update to the current state of affairs. We may end up needing a more official trait after all, but it may also be best to flesh out a bit first and see if it comes up.

from futures-rs.