Gladaed comments on I love new features

[–] Gladaed@feddit.org 18 points 2 years ago* (4 children)

Because stuff can own other stuff and be owned at the same time. Also, arcane jackarsery.

Edit: if you want to give a function a pointer that it may change this may occur in a constructive way. I.e. replace an owned object.

parent

[–] marcos@lemmy.world 5 points 2 years ago (3 children)

Yeah... But it's usually a good practice to put a struct somewhere between your 30 levels of ownership.

Exceptions exist, but they are not very common. Also, in C++, operators overloading may help you if you keep needing to write code like this.

parent

[–] Gladaed@feddit.org 3 points 2 years ago (2 children)

In C++ you should never have owning raw pointers. Unless you have a good reason™.

Raw pointers are great, but not for ownership.

parent

[–] qaz@lemmy.world 6 points 2 years ago* (last edited 2 years ago) (1 child)

I just use unique_ptr 99% of the time

parent

[–] Gladaed@feddit.org 4 points 2 years ago

And you should.

It even works for classes whose constructors your implementation cannot see, if you aren't a bitch about it.

parent