Subject: Re: [boost] [thread] Dividing into Boost.Thread and Boost.Sync
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2013-08-17 08:47:05
On Saturday 17 August 2013 13:54:57 Klaim - JoÃ«l Lamotte wrote:
> On Sat, Aug 17, 2013 at 1:41 PM, Andrey Semashev
> > We haven't discussed Boost.Async, just Boost.Sync for now. It seems
> > possible,
> > although I wonder what will be left in Boost.Thread then? Basic thread
> > management?
> Sorry that was a typo, I meant Boost.Sync yes.
> It's true that Boost.Thread would host only boost::thread and interruptions
> then, so the split I was wondering about might not really helpful,
> I was just wondering because future/promise/async are, to me,
> synchronization mechanisms, but high-level compared to the ones you already
> want to separate,
> so I would have expected to find them with other "synchronization"
> mechanisms, OR in a high-level synchronization mechanism library.
> Future/promise/aysnc are all packed into <future> in the standard library
> by the way, not sure if it's the best grouping but it's notable data.
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.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk