Subject: [boost] [any] Move semantic
From: Klaim - JoÃ«l Lamotte (mjklaim_at_[hidden])
Date: 2012-05-17 04:33:26
My current understanding of the new rules of 5 tells me that boost::any
isn't "move aware".
First, am I correct?
Second, I think that adding the move constructor and move operator is
Again, am I correct or is there some tricks to know before adding them?
Third, I want to use boost::any in a value-semantic type. Sometime it would
keep a unique_ptr.
If I understand correctly move semantic and unique_ptr implementation, the
current boost::any implementation don't forbid me to use
unique_ptr as a value type.
Am I correct?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk