On Saturday, 27 June 2015 at 03:16:35 UTC, rsw0x wrote: > calling destroy on a pointer should either be fixed or be an > error, that should not be allowed to happen. Completely agreed. Calling destroy() on a pointer has been incorrect EVERY time I've seen it done.