unittests are really part of the build, not a special run

[Mathias Lang via Digitalmars-d]

I'd rather see DMD automatically pass the expression that triggered the
error (as it is done in C) to replace this useless "Unittest failure" that
forces me to look through the code.

D has the advantage that it catches most errors at CT. You can write a lot
of code and just compile it to ensure it's more or less correct. I often
write code that won't pass the unittests, but I need to check if my
template / CT logic is correct. It may takes 20 compilations cycle before I
run the unittests. Running the tests as part of the build would REALLY slow
down the process -especially given that unittest is communicated to
imported module, which means imported libraries. You don't want to catch
unittests failures on every compilation cycle, but rather before your code
make it to the repo - that's what CI systems are for -.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20150331/3086af3c/attachment.html>