[dmd-internals] assert inside unittest still sucks

Sean Kelly sean at invisibleduck.org
Fri Jul 23 09:51:00 PDT 2010


On Jul 23, 2010, at 8:24 AM, Andrei Alexandrescu wrote:

> Sorry for bringing this up again. I still dream of the good ol' assert. Right now with the latest druntime, assert(expr) goes completely silent. No message at all. The program exits with errorcode 1, but you have no idea what happened.

In the last thread someone suggested providing an overridable routine that prints unhandled exceptions during the unittest run.  How about that?  I'd left it silent thus far to avoid cluttering specifically formatted unittest results with runtime-level output.


More information about the dmd-internals mailing list