17 Aug
2013
17 Aug
'13
3:58 p.m.
2013/8/17 Andrey Semashev
We don't plan to extract futures and related stuff, it's too coupled with Boost.Thread. The main goal of Boost.Sync is to provide lightweight building blocks for low level thread synchronization and futures are beyond that.
futures usually depend only on mutex and condition_variable - at least it is possible to implement it this way. I would vote to decouple boost.future from boost.thread (so it could be used from other execution primitives than threads).