Date: 2007-03-20 10:04:28
> > I suggest that
> > future< tuple< T1, T2, T3 > > f_and( f1 && f2 && f3);
> future< variant<
> > T1, T2, T3 > > f_or( f1 || f2 || f3);
> > behave like ordinary futures f1, f2, f3.
> > That means the the current thread is blocked in future< T
> > >::get() not in the ctor.
It should be also possible to get the information from which future the
result is taken.
> Sure, that's the exact behavior of the future's library in the Vault.
The problem with the futures library in the vault is that sometimes it
raies an assertion - this well known by the author but he don't know why
this is raised and how to fix.
Boost list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk