Blog post about printing associative arrays from GDB

kinke noone at
Wed Oct 23 21:10:01 UTC 2019


> Now wouldn’t it be even more useful if we knew why the unit 
> test failed? Apparently D doesn’t print that information 
> automatically on assertion failure, supposedly for performance 
> reasons.

Off-topic, but recent frontends feature a `--checkaction=context` 
switch, which for your example yields something like:

onlineapp.d(5): [unittest] [3: 30, 2: 20, 1: 10] != [1: 10]
1/1 unittests FAILED

More information about the Digitalmars-d-announce mailing list