On 23 May 2018 at 15:47, sarn via Digitalmars-d <[email protected]> wrote: > On Wednesday, 23 May 2018 at 02:13:13 UTC, rikki cattermole wrote: >> >> I would consider the current state with classes a bug. >> So ticket please, it should not require a DIP to change (although Walter >> may disagree). > > > Unfortunately, the way __dtor and __xdtor work for classes can't be changed > without the risk of breaking code. (Even if the current behaviour is > broken, users might be working around it.)
In what way is the current behaviour *broken*? (as opposed to awkward, confusing, and poorly documented)
