Generated opAssign in the presence of a copy constructor

[12345swordy]

On Thursday, 26 July 2018 at 09:40:03 UTC, RazvanN wrote:
> Hello everyone!
>
> As you probably know, I am working on the copy constructor DIP 
> and implementation. So far, I managed to implement 95% of the 
> copy constructor logic (as stated in the DIP). The point that 
> is a bit of a headache is how/when should opAssign be generated 
> when a copy constructor is defined. Now here is what I have 
> (big thanks to Andrei for all the ideas, suggestions and 
> brainstorms):
>
> [...]
Why are you not using the destroy() function?

-Alexander