Boost logo

Boost :

Subject: Re: [boost] [thread] terminating destructor
From: Olaf van der Spek (ml_at_[hidden])
Date: 2012-10-25 04:03:40


On Thu, Oct 25, 2012 at 9:56 AM, Andrzej Krzemienski <akrzemi1_at_[hidden]> wrote:
> The third situation below shows a non blocking ~future. But such execution
> is *disallowed *by the standard because the completion of launched thread
> would not synchronize with the last release of the shared state.

The big question is: why?

Can't the destructor detach from the shared state and let the state be
cleaned up by the launched thread?

Olaf


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk