unittest affects next unittest

[Era Scarecrow via Digitalmars-d-learn]

On Tuesday, 5 August 2014 at 17:41:06 UTC, Marc Schütz wrote:
> It's a consequence of the fact that every type in D has a 
> default initializer which is known at compile time.

  Then doesn't this mean it should pop out a warning in case 
that's the behavior you wanted, perhaps a reference to the D 
specs?

  Beyond that it would be easy to forget it does that, since class 
initializes things different than structs because of the 'known 
at compile time' logic.