Subject: Re: [boost] Futures
From: Mathias Gaunard (mathias.gaunard_at_[hidden])
Date: 2015-01-04 18:01:57
On 04/01/2015 16:55, Sebastian Schaetz wrote:
> Thomas Heller <thom.heller <at> gmail.com> writes:
>> Interesting. Let me try to explain what I am seeing in the future concept
>> and try to translate that async_result:
>> For me, the concept behind futures is twofold, you have the future<T> on the
>> *receiving* side which is, apart from the return type of the async operation,
>> a completely type erased (as in type of asynchronous operation) handle to a
>> future result. Things like promise, packaged_task or whatnot represent the
>> *sending* side of the operation.
> I'm really happy about this discussion here. Can you clarify what you mean
> by a future being type erased? You don't mean to say a future is a
> future<any>, do you?
Presumably that the type of the future does not contain the type of the
callable function object it contains, thus requiring dynamic memory
allocation and indirection.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk