• Gladaed@feddit.org
    18·
    7 days ago

    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.

    • marcos@lemmy.world
      5·
      6 days ago

      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.

      • Gladaed@feddit.org
        3·
        6 days ago

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

        Raw pointers are great, but not for ownership.

          • Gladaed@feddit.org
            4·
            6 days ago

            And you should.

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