Boost C++ Libraries: Ticket #9171: Boost.Type_Erasure should be move-aware regarding construction. https://svn.boost.org/trac10/ticket/9171 <p> boost::type_erasure::any does not perform move-construction of the contained object during construction of the encapsulating any due to boost::type_erasure::detail::storage's constructor template not using perfect forwarding. This is particularly a problem because it means that you cannot construct an any with a move-only type, which has come up in practice. Similarly, it would be nice to have a "make_any" function template that is able to do completely in-place construction of the contained object. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/9171 Trac 1.4.3 Deniz Bahadir <D.Bahadir@…> Tue, 11 Feb 2014 18:31:36 GMT <link>https://svn.boost.org/trac10/ticket/9171#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/9171#comment:1</guid> <description> <p> I would also very much appreciate if the concept of <strong>move_constructible</strong> could be added to <em>Boost.Type_Erasure</em>. At least for C++11. However, maybe it is also possible to implement it for C++03, too, by using <em>Boost.Move</em>? </p> <p> I actually found this (<a class="ext-link" href="http://thread.gmane.org/gmane.comp.lib.boost.devel/243109"><span class="icon">​</span>http://thread.gmane.org/gmane.comp.lib.boost.devel/243109</a>) conversation between Christophe Henry and Steven Watanabe in which Christophe shows a possible implementation of <em>move_constructible</em> concept.<br /> However, it does not seem to work (at least for GCC 4.8 with C++11 enabled). </p> <p> (PS: In my special case I would like to type-erase a class which has a std::unique_ptr member.) </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Steven Watanabe</dc:creator> <pubDate>Tue, 11 Mar 2014 20:37:21 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/9171#comment:2 https://svn.boost.org/trac10/ticket/9171#comment:2 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> <p> It seems to be fixed now. </p> Ticket