We'd still vote 7kyu no matter what fwiw. The optimisation is the most trivial observation possible.

You're right. My intention was to make it a 7 kyu kata, which is why I was a bit lazy with the random tests. Anything over 10^4 would make it a 6 kyu.

Feel free to create a fork—I'll approve it.

it doesn't work for the example tests ( which are also included in the submit tests ).

the fixed and random tests would have to test explicitly and separately if the return value is a number, because they convert it to a string anyway for testing. I don't think that's necessary.

JS probably has exactly the same situation.

fixed

yes

Done!

Great catch. My bad. On it.

This kata has broken my spirit, well done :)

EDIT: nevermind, you answered in the comments below.

For this type of kata, that's bound to happen.

A specific subset of the total sulutions will fall under this realm of barely passing.
Even if the test cases were the same all the time, there would still be some variance.

Best I can do is add a note saying that if your solution barelly passed (about 10 test cases missing), keep trying.

Solutions that are very unnoptimized still won't pass, while that subset will.

I'm sorry I didn't solve your issue, I just don't see what I can do about it.

For some reason, I thought of this case as inability to get to target num, if num%4==0, rather then infinite solutions
Thank you for feedback, made description more specific for that case

removed MY_ASCII_HASH. added randomization to random tests.

Added them. Thanks for the suggestion!

And is it possible for you to approve this? https://www.codewars.com/kata/64b84ed4b46f91004b493d87
It's been awaiting approval for two months! When I ask on Discord about it, people say they haven't solved it, so they can't approve it. I'm sort of getting desperate.

I think it's fine now - the last two test sample cases are

{5, 25, 21, 19, 17},

{10, 123, 946, 952, 954}.

dfhwze, if you could approve, that would be much appreciated!