From: Ion Gaztañaga (igaztanaga_at_[hidden])
Date: 2008-05-19 11:22:01
Anthony Williams wrote:
> "Dean Michael Berris" <mikhailberis_at_[hidden]> writes:
>> Right now, having futures non-default constructable makes it hard(er)
>> to put them in standard containers.
> The futures in my proposal can be default-constructed. unique_future requires
> a move-aware container, but shared_future should be usable in any container.
Just to add a little bit more information. When move semantics emulation
are unified, Interprocess containers (their default allocator is
std::allocator<T>) could be used to store unique futures. This would
include map/set, family flat_map/set family, list, vector and deque.
boost::unordered_map would also be compatible with non-copyable types.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk