Now it's clear. Thanks to both of you :)
Jonathan M Davis:
> If a static assert is in a unit test block it's to verify that something
> works. You don't necessarily want it in normal code. For instance, what if
> the
> static assert is verifying something about a templated type or function?
> Having that static assert in the normal c
On 2011-03-29 10:08, Piotr Szturmaj wrote:
> I see this is common practice in Phobos. I though static asserts should
> be checked at each compilation, not only when compiling with unittest.
> Or is it supposed to shorten compile time for already tested modules? :)
If a static assert is in a unit t
