I wish that the #rustlang assert_eq!() macro had a convention for whether the expected value should be first or second. I always have to go puzzle through the source code to figure out which argument was the wrong one.
=> More informations about this toot | More toots from blp@framapiaf.org
@blp Its annoying when making fancier asserts, like snapbox::assert_data_eq
which shows a diff because we have to be prescriptive about it.
=> More informations about this toot | More toots from epage@hachyderm.io
text/gemini
This content has been proxied by September (ba2dc).