id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc
13165,inplace_ptr,gast128@…,Peter Dimov,"Boost.Optional uses in place object creation. In many cases it could used as a drop in repelacment of scoped_ptr with the benefit of circumventing a memory allocation and locality of memory access.

However its semantics is 'optional' and not like a fast replacement of scoped_ptr. Wouldn't it be an idea to add something like this to  the smart_ptr library? Names can be e.g. inplace_ptr, value_ptr, etc. We could also use Boost.Optional but colleagues might get confused, since you do not use the 'optional' aspect but its performance aspect.

Note that people might wonder why not use value based directly, but there are still some use cases:
* for pimpl idiom / hide expansive headers (e.g. multi index) in client
* 2 phase construction, where information is not yet available at parent constructor time.

Only drawback is that you lose polymorphism.

https://stackoverflow.com/questions/22636407/why-not-use-boostoptional-as-a-better-scoped-ptr",Feature Requests,new,To Be Determined,smart_ptr,Boost 1.64.0,Not Applicable,,,