it looks like the random tests in C# now include large numbers that dont fit in 64-bit integers

Python fork.

It's a bit jank and it uses some hardcoding on my part. It's still possible for the user to hardcode it, but it would be considerably harder.

If you implement a code length check, then it should be very safe, but you'd have to mess with the description. To be honest, that would probably be a good idea.

"The others are just as bad" isn't an excuse. The kata as a whole has issues, it would be good to fix those before approving more translations.

Also, exploiting bad specs isn't cheating, if you don't want people to exploit the tests, then write better tests.

@KayleighWasTaken: Yes, I approved the Python translation, and I think it's OK. Its tests aren't any worse than those for Java and JavaScript. I wasn't complaining about the Python translation. I just was a bit disappointed that literally minutes after I approved it, someone posted a cheating "solution" that took advantage of the lack of randomness in the tests.

I'm working on tests that will be much more random than the current tests. I think I'll need a day or two.

Aren't you the one who approved the Python translation?

...and now Python as well. :-(

Question has been answered.

Correct solution is to change interface to be a stream of BigInteger and write proper tests rather than the current meme tests.

Thanks for the report! I've been messing with this for a bit and the more I try the less idea I have on why this happens. Java is weird! I don't know when, if ever, I could fix this, but if at any point you have good ideas do share!

I guess you mean Java?

Hmm, which edge cases that fall into the category "positive, non-zero digits"?

• You raise issue because it is banned.
• And previously people raise issues when it allowed too many solutions abusing java.util functions

There is no middle ground.