JS version got updated (it had a serious bug in tests), and this issue should be resolved.

Problem is the stringifying the testing does. Should use Test.assertDeepEquals instead of Test.expect . (===) `on` String.

It is an issue and it can be solved, but I don't think the world will stop turning if it isn't.

.

I actually ran into the same issue. This needs to be solved.

What, did you even look at the examples in the description?

Issue solved.

Do you think this note at the end of the description solves the issue?

IMPORTANT: The correct spelling of "Pokémon" is "Pokémon", with the "é", but to maximize the compatibility of the code I've had to write it as "Pokemon", without the "é". So, in your code, don't use the "é".

Can you be more specific? I think I have already changed all 'é' into 'e'....

By that I mean that cheaters are welcome to cheat their way into this... if they can :)

any use of numbers will cause it to fail, not an issue.

You could get a string with two "--", plus I see no point in doing to...

Sorry I can not get the point... do you mean isPrime could be replaced with some cleverer way?