[Issue 15044] [Reg 2.068.0] destroy might leak memory

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=15044

--- Comment #3 from Kenji Hara <k.hara.pg at gmail.com> ---
(In reply to Martin Nowak from comment #2)
> Any idea how to solve this @Kenji?
> We could try to do semantic3 for buildOpAssign later, but then we'd have to
> add a special case to op_overload and gag assign usage or so.

I think currently there's no way than treat the generated opAssign function
specially.

I'll post a PR soon.

--