This is a big problem for me because, in my application, I've realized unittests as functions called from within static shared module constructors to elide the problem of unittests being enabled recursively, which slows down iterative compilation time enormously.
AFAICT, stacktraces are not emitted with debug information when
errors occurr in static module constructors. Is this a know bug?
- Stacktraces in static constructors Nordlöw via Digitalmars-d-learn
- Re: Stacktraces in static cons... Nordlöw via Digitalmars-d-learn
- Re: Stacktraces in static ... Benjamin Thaut via Digitalmars-d-learn
- Re: Stacktraces in sta... Nordlöw via Digitalmars-d-learn
- Re: Stacktraces in... Benjamin Thaut via Digitalmars-d-learn
- Re: Stacktraces in static cons... Nordlöw via Digitalmars-d-learn