Re: [boost] [next gen future-promise] What to callthemonadicreturntype?

Gottlob Frege wrote:

Can't use a spinlock pool. Because you might hold the spin lock when moving/copying T, and T could be anything, then, in theory at least, T's constructor might also use a future/promise, etc, etc, such that a collision could cause a deadlock.

Yes, good point. Need recursive spinlocks.