approved.

Sorry for getting back to this so late (notifications don't work and I forgot this existed)

Is there a reason random tests all have the same length? If those were to be random, then this is approvable.

Added description for what left and right are to assert_eq! message.

The main issue with Rusts default assertions is that it assumes that whoever is authoring the code is also authoring/viewing tests. Here it is not so, and users have no idea what left and right refer to. A line clarifying which is which should always be added to the assertion of assert_eq!.

Works in Rust 1.6.6.

Assert messages now include the input (first 3 elements for long inputs).

Using super::find_uniq.

Fixed description merge conflict (as of now).

Added more descriptive names.

Using char literals in place of ascii codes for clarity.

Non-pangram branch in random test no longer has chance of randomly generating pangram so we don't need to check reference_solution.

Updated to use gen_range(1..3) as it accepts a range as of rand 0.8.0 https://docs.rs/rand/0.8.0/rand/trait.Rng.html#method.gen_range

Works on Rust 1.6.6

Hi, just a minor typo: comming should be coming

.

Indeed, the example tests case were not calling the right function.
It is now fixed

The lua sample tests call a function solution.gloves instead of solution.number_of_pairs, so you fail the sample tests unless you change the function name to gloves. However you need to use the function name number_of_pairs for the actual attempt. (Also Exemple test is misspelled.)

I suggest clarifying in the description that payments cannot be negative or 0. It's a valid restriction but it should be explicit in the specifications rather than only through the test cases IMO.