From: Johan Torp (johan.torp_at_[hidden])
Date: 2008-05-30 09:50:19
Anthony Williams-4 wrote:
>> I don't think your proposed interface is powerful enough to implement
>> composed futures, but I might be wrong. For instance, how would you
>> implement future operators with it?
>> future<bool> operator||(future<bool> lhs, future<bool> rhs);
> Using wait callbacks:
is_ready doesn't trigger the callback, so this won't work.
OTOH, I think is_ready should trigger the callback, even for the "run extra
work in wait()" thread pool use case.
-- View this message in context: http://www.nabble.com/-future--Early-draft-of-wait-for-multiple-futures-interface-tp17242880p17559352.html Sent from the Boost - Dev mailing list archive at Nabble.com.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk