Re: [Boost-users] [MPL] initialization of member that might be non-copyable

Subject: Re: [Boost-users] [MPL] initialization of member that might be non-copyable
From: Larry Evans (cppljevans_at_[hidden])
Date: 2011-03-26 09:15:10

On 03/25/11 15:48, Noah Roberts wrote:
> I'm working on something similar to the construct devised in the MPL
> book Section 9.5 (class composition).  Some objects in the composed type
> might require initialization.  I've solved this problem.
> 
> However, in solving that problem I've now required that any type going
> into the composition must be copyable.  However, since the original
> composition code doesn't make this requirement I've been trying to find
> a way to retain the ability to contain types that are non-copyable.
[snip]

So, I guess you've looked at the other container types in boost,
such as fusion's vector:

http://www.boost.org/doc/libs/1_46_1/libs/fusion/doc/html/fusion/container/vector.html

and found them lacking in this regard. IOW, with these other container
types, all the contained types must be copyable?

-Larry