Re: [boost] move semantics

From: Greg Colvin (gcolvin_at_[hidden])
Date: 2002-02-05 19:29:32

From: "Sean Parent" <sparent_at_[hidden]>
> Thinking this through - I think I need to add to my previous list of
> requirements on T for these containers.
> 
> T must provide a move constructor.
> 
> A move constructor constructs a new T from a source T, leaving the source in
> an indeterminate but destructible state.
> 
> The "copy" constructor for an std::auto_ptr meets this requirement.

So this type of container can safely hold an auto_ptr?