search for: getclear

...call 'release()" on the unique_ptr to ensure ownership was never really taken). > We had three derivative types of pointers > (Shared/Owned/Linked) which would just differ on the default behaviour > of construction / destruction, but all of them could still explicitly > call getClear / getLink / etc. > > The downside was that almost every interaction with smart pointers had > to be carefully planned and there was a lot of room for errors, > My hope is that having a single construct for conditional ownership will be less confusing than the existing ad-hoc solutions...

On Wed, Sep 24, 2014 at 7:50 PM, Justin Bogner <mail at justinbogner.com> wrote: > Anton Yartsev <anton.yartsev at gmail.com> writes: > > Hello everyone, > > > > I bring to discussion the necessity/design of a new type of smart > pointer. > > r215176 and r217791 rise the problem, D5443 is devoted to the solution. > > r215176 applies several