On Thursday, 28 February 2019 at 01:42:13 UTC, Andrei Alexandrescu wrote:
Such sharing of resources across objects is a common occurrence, which would be impeded by forcing `const` on the right-hand side of a copy. (An inferior workaround would be to selectively cast `const` away inside the copy constructor, which is obviously undesirable.) For that reason this DIP proposes allowing mutable copy sources.

There's an argument to be made that a copy constructor isn't the best way to share resources between two variables in a way that might affect code using the variable being copied.
              • R... Walter Bright via Digitalmars-d-announce
      • Re: DIP 1018--The ... Jacob Carlborg via Digitalmars-d-announce
        • Re: DIP 1018--... Andrei Alexandrescu via Digitalmars-d-announce
          • Re: DIP 10... Paolo Invernizzi via Digitalmars-d-announce
            • Re: D... Andrei Alexandrescu via Digitalmars-d-announce
            • Re: D... Paul Backus via Digitalmars-d-announce
            • Re: D... Olivier FAURE via Digitalmars-d-announce
              • R... Olivier FAURE via Digitalmars-d-announce
              • R... Walter Bright via Digitalmars-d-announce
            • Re: D... Andrei Alexandrescu via Digitalmars-d-announce
              • R... Olivier FAURE via Digitalmars-d-announce
          • Re: DIP 10... Nicholas Wilson via Digitalmars-d-announce
          • Re: DIP 10... Jacob Carlborg via Digitalmars-d-announce
  • Re: DIP 1018--The Copy Cons... RazvanN via Digitalmars-d-announce

Reply via email to