Thanks a lot! Much appreciated!!!

You're welcome ;)

Oh I see... that is highly unlikely to ever happen, isn't it? It's not exactly a popular kata, so I wonder how a translation will make its way here. I wanted to translate it to try and get more users to it, I think its a nice kata :)

The author is missing, so you have to wait for a power user to solve it in Ruby first and then review and approve your translation.

Bump. Does anyone know how to get a translation published?

Nice kata! Added JavaScript translation.
https://www.codewars.com/kumite/5bba064b2d15ec331d0000ff?sel=5bba064b2d15ec331d0000ff

I'm not sure how it will help you if I type the name of some IDE into here. Let's just end this discussion, it has clearly derailed from the original post.

And what is the "other environment"? ;-) When you raise an issue you need to give the details, or how do you expect others to look into it? We can't read your mind.

What I mean is that the execution does not stop because of time out at making the 'attempt'. I'm assuming something is broken on the grounds that it works fine in other environments.

The time spent by a blank submit is not the time it takes for the reference solution to run the tests because you also have to take account for the time to generate random test cases. When the test case size is large this is actually a very heavy operation (at least O(n)).

But in any case, since the kata needs to be published with a working author solution it can be passed. "I can't pass the tests" is not a valid ground for an issue, but instead a question ;-)

So then code speed isn't the issue because the solution doesn't reach anywhere near that limit

What's the problem with 700ms? That leaves you with 11300ms to spare, so your code can even be 15 times slower than the reference solution.

I'm not sure. Even if I cut the code, and leave it at 'return n', it's still 700ms. Can you please look into it?

List generation takes lots of time. Submitting pass takes 9 seconds, while submitting an actual solution takes the same 9 sec. Also, it's not critical.

Your code is too slow.