There is a typo in "RecieveDamage".

You made my day)

Cool and tricky

LOL

• Updated to Rust 1.66
• Added assertion messages
• Added a fixed test that contains identical numbers

Added some time ago

No longer an issue.

Thank you for reviewing that.

There is no point in forking a translation just to update the original solution (which would end up published in the original author's name anyway). Especially when there are other things that actually need fixing, e.g. missing assertion messages.

Rejected.

Dude

If there are test cases which always expect some specific answer consistently in the same invocation, it makes test cases suspectible to counting. Users can use a global variable to count invocations of their solution, and return true, false, or None or some other predictable result for every expected n-th invocation.

This problem might not be especially relevant for some kata, the most affected kata are the ones which expect bool as an answer, but the general practice is that for random tests, the expected results (and their order) should be unpredictable This can be achieved for example by generating a list of inputs for all tests, and then shuffling the list.

How does having separate tests expecting None make it easy to cheat?

AHAHAHA, nice

That's how I feel after an acid trip six years ago, like an Inception spinning top in the depth of my unconscious.

Doesn't this fail when an element appears thice?
It looks like repeats(&vec![1, 1, 1]) would result in -1