On Wednesday, 3 September 2014 at 22:34:30 UTC, Kevin Lamonte
wrote:
I've got a feature request in for just that:
https://issues.dlang.org/show_bug.cgi?id=13406
Interesting! I am not 100% convinced that scope(failure/success)
is the way to go since it will cause potentially a lot of extra
work when unwinding the stack in case of an exception? Or maybe
the stack unwinder could to the tracing directly without using
the scope construct.
Another option would be to only trace the landing-pad ("catch
statement") for exceptions, so you would get something like
"exception X caught in functionname()", but not sure how to do it
without loosing information. You might need a counter for each
enter/exit or something like that and let the stack-unwinder
count down.
