Peter Dimov-5 wrote:
In a previous post you said "Limiting the reuse to pool threads eliminates most other (theoretical IMO) problems.". What theoretical problems has been identified with thread re-use?
"State" leaking from one thread to another via thread-local variables, thread priority, or thread stack size.
Given that thread's stack size can be increased for worker threads, these problems doesn't seem to justify the complexity of the explicit yielding I proposed. It has another benefit though, you can implement "thread reuse" without exposing the future::set_wait_callback function. Johan -- View this message in context: http://www.nabble.com/-thread-pool-futures--Explicit-yielding-tp17606225p177... Sent from the Boost - Dev mailing list archive at Nabble.com.