the compiler probably optimizes it away anyway

战神

A couple optimizations are warranted:

• Remove the last 2 lines of the code block in the description and add to the plain text description
• You can implement the random string generator as (repeatedly len #(rand-nth "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz"), or something similar with rand-nth

Best performance

Please use spoiler flag next time. Your post was visible in the homepage discourse.

..|..

This issue is fixed

duplicate issue

Can someone explain how

"11111" expects [0] = "Pinkie", [1] = "Ring", [2] = "Middle", [3] = "Index", [4] = "Thumb"

but

"11101" expects "Index" to be returned ??

This is in C# random tests.

How does one come up with this?

Same with all katas by g964, they are math puzzles. Not coding puzzles.

Be nice if we could just block all katas by certain users.

If I'm understand the random test output correctly for golang, I'm seeing random tests like this:

[[0 0 0 0 0]
 [0 0 0 0 x]
 [0 0 0 0 0]
 [0 0 0 0 ^]
 [0 0 0 0 0]]

which expects the answer to be false.

Similar:

[[0 0 v]
 [0 0 0]
 [0 0 x]]

Where 118 is v and 120 is x

The test is expecting this as false...

Random tests are even failing on some 3x3s, but I've added every combo of <>^v and x possible in a 3x3 grid, with correct expected results in a 3x3 grid to the sample tests and they all pass.