27 Mar
2015
27 Mar
'15
8:16 p.m.
On Wed, Mar 25, 2015 at 8:55 AM, Jakob Riedle
A null-deleter would make it basically non-owning..
That doesn't solve Efficiency, but it allows for non-owning shared_ptr's. Thank you!
It doesn't, however, solve the underlying safety issues. Smart Pointers tend to be smart in two ways: - track ownership to correctly delete object - be safe With flex_ptr (or shared_ptr with custom deleter), how do you know that a non-null flex_ptr is pointing to valid memory or not. Or if it is valid on this line, but not the next, due to threading or something. Tony