Oh hell nah now I have paranoia

a game developer

No not agaaaaaain 😫

Waiting for console graphincs of this kata!

Descriptions are generic, it is clear what tests expect when one sees the code.

• Resolved description merge conflict

• Bumped to 1.62 && made corresponding changes

• Prevent initial solution from UB

• Added useful assertion messages, actual and expected outputs

• Inputs are tested up to half of maximum range of unsigned integer

Great calculations! Awesome))

Awesome!

When s2 is just a shuffled part of s1, we know the result is true, there is no need to check with reference solution. When s2 = random_string(s2_len); is executed, the previous statement let mut s2: String = s1.chars().take(s2_len).collect(); is overwritten and useless.

Vote Funny

FIxed some time ago

I don't think it's a good practice in Rust to import inside a function.

I think it's a good idea to use a tuple rather than an overwhelming struct or hashmap or whatever. However I would add an explicit note in solution set up so the user knows exactly what is expected in the tuple.

Added in the next fork

I suggest to add this random test, which makes fail some invalid solutions that pass all tests most of time otherwise:

  assert!(! is_valid_walk(&['e', 'e', 'e', 'e', 'w', 'w', 's', 's', 's', 's']))

You can refer to an issue I raised 10 months ago. The issue is present in all languages except Java (but this one has no random tests...). Ideally we should make sure to generate random tests such solutions to pass (but it could be complicated..., not sure it really worths it).

Updated in most recent fork! Thanks for taking a look