7 Mar
2013
7 Mar
'13
2:14 a.m.
On Wed, Mar 6, 2013 at 10:46 AM, Hartmut Kaiser
I'd strongly suggest not to add <foo>_async_after(). All we need is
a) a function/algorithm producing a future b) composable futures (see N3428, http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3428.pdf)
But for this to be universally applicable we should try to find a way to converge onto ONE future type.
Very interesting, thanks for posting this. I'll take some time to think on how best to integrate these concepts with Boost.Compute. And yes, I would be very supporting of a generic and general solution. -kyle