Subject: Re: [boost] [thread] Dividing into Boost.Thread and Boost.Sync
From: Oliver Kowalke (oliver.kowalke_at_[hidden])
Date: 2013-08-17 11:58:52
2013/8/17 Andrey Semashev <andrey.semashev_at_[hidden]>
> 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).