25 Oct
2012
25 Oct
'12
8:03 a.m.
On Thu, Oct 25, 2012 at 9:56 AM, Andrzej Krzemienski <akrzemi1@gmail.com> 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