79 karma · joined July 26, 2020
Without `rustfmt::skip`, rustfmt would break these sections into more lines but I prefer them to look like little tables.
Therefore the tool should run the tests in random order, to flush out the non-decent tests. IMHO.
> `assert!(!xs.is_empty(), "expected parameter 'xs' to be non-empty")`.
This panics with
> thread 'main' panicked at 'expected parameter 'xs' to be non-empty', src/main.rs:79:5
Without the custom message it's
> thread 'main' panicked at 'assertion failed: !xs.is_empty()', src/main.rs:79:5
Given that panics should be for bugs, i.e. interpreted by developers, I'd say the second message is clear enough and a custom message just adds noise in the source code.
A letter in Morse code is made of up to four “dits” or “dahs”. Why would it take more than two minutes to send one letter?