Improve reporting of location failed assertion
Brought to you by:
malange
Menu
▾
▴
#35 Improve reporting of location failed assertion
Although file and line number are reported for assertions (if debug information is available), this is only limited information.
It would be better to have some easier to use representation of the entire call stack for the failed assertion, or the unexpected exception.
Logged In: YES
user_id=280452
Originator: YES
Similar it would also be good if the Expected vs. Actual would become easier to assess.