Please review my Rust translation!

It should panic, according to the description that's an invalid input.

If you enter 11 the code will panic. I don't think this is a "best practice."

Just started my rust journey and found your solution.
Then I went to test it.
Somehow misstyped "yello" and found the bug.
Endless loop at .skip_while stage. SatCat

Assertion messages need to be improved such that the user is made aware which is expected and which is actual. This is particularly important for beginner level kata.

I've just bumped the version

Numbers above 3999 are wrong and should not be tested.

Approved by someone

Could you include more explicit assertion messages? The default ones are not clear, and it's better to provide the input.

I think it's better practice to explicitly import the user's solution:

    use super::find_uniq;

Also, this translation needs to be updated to the latest version.

That filter() was really clever!

• Tests case throw an error (bad recursive call);
• Needs update to 1.60

ugh
.split_last()

Approved

Please use a spoiler flag, comments are visible to everyone by default (I've just put the flag on for you).