'you don't have to consider things like undefined, null, NaN, negative numbers, strings and so on.'

But as the Math object has been reset you shouldnt use Math.floor in the first method Math.round

.

Fixed and random cases with symbol characters are now tested. Closing.

yes, but in JS it is definitely harder now than in Python.

Yes

You are correct. I made mistakes. Just fixed them.
They did not change results. So no one noticed.
Thank you very much!

If my testcode run correctly there should not be things like ABA. I modified the testcode from another kata I made which may have certain disconnected cases. Maybe I missed something. Did you see this type of disconnected areas in the tests?

Thank you so much for pointing out the typo. I corrected it.

Not an issue, but a suggestion. Anyway, I removed that test, as there were other complaints earlier about it.

Yup, you got it right o_O

But it's already there? Upper limit for n is specified as 10^16, isn't it?

Modified Kata description as follows

• Before: When you arrive at the destination return the final coordinates.
• After: When you arrive at the destination return the final [x,y] coordinates.

Duplicate issue, closing this one.

Thanks for that, you right! I've updated the Kata. Back then I possibly fooled myself, because NaN and Infinity is autoboxed into a Number without the need of () or space after 1. <- dot.

After three years ?!?

Much more elegant, I like that solution a ton! Thanks for the kind words and the great tips!