When running a test using invariants with tasty-dejafu, when an invariant is violated, all it shows is invariant failure with a trace. I believe this comes from the showCondition function, which doesn't display the inner exception of an InvariantFailure but does include this in the UncaughtException case.
Since my code checking invariants throws exceptions with some message explaining which invariant was violated, it'd be useful to have this displayed so at least I know what's causing the failure (it's not clear from the trace, could be a bug in my invariant check as well).
Is there a particular reason why the exception is discarded? If not, could it be added similar to the UncaughtException case?
When running a test using invariants with
tasty-dejafu, when an invariant is violated, all it shows isinvariant failurewith a trace. I believe this comes from theshowConditionfunction, which doesn't display the inner exception of anInvariantFailurebut does include this in theUncaughtExceptioncase.Since my code checking invariants throws exceptions with some message explaining which invariant was violated, it'd be useful to have this displayed so at least I know what's causing the failure (it's not clear from the trace, could be a bug in my invariant check as well).
Is there a particular reason why the exception is discarded? If not, could it be added similar to the
UncaughtExceptioncase?