On Wednesday, 22 October 2014 at 16:55:41 UTC, Regan Heath
So why wasn't the eles' destructor order in reverse if Scoped is a struct and calls explicit destroy(B) then destroy(A)?
Maybe it's the writeln() inside the destructor which behaves badly, albeit the same should have happened for structs too.
