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

2015-09-14 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15044 --- Comment #3 from Kenji Hara --- (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

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

2015-09-11 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15044 Martin Nowak changed: What|Removed |Added CC||k.hara...@gmail.com ---

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

2015-09-11 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=15044 --- Comment #1 from Martin Nowak --- This breaks b/c of the following semantic analysis issue. Vector.semantic dup.semantic RefCounted!Vector.semantic (return type) RefCounted!Vector buildOpAssign RefCounted!Vector.dtor.semantic3