6 May
2015
6 May
'15
2:09 p.m.
On Wed, May 6, 2015 at 4:55 PM, Ion Gaztañaga
Another issue is if we should put it into Boost.SmartPtr or not, specially the documentation. To minimize th work we can add a small section in Boost.SmartPtr's documentation that points to Boost.Move documentation, as someone looking for boost::unique_ptr is likely to start looking in Boost.SmartPtr.
+1 to "someone looking for boost::unique_ptr is likely to start looking in Boost.SmartPtr". I think it is logical to have it in Boost.SmartPtr (implementation, docs and tests).