Also, in this case it doesn't matter at all because the answer already becomes infinity well before n = 1000. You're just not going to supply a number bigger than recursion limit (which is typically at least a few thousand).

It's OK. TCO (tail-call optimization) is implemented in ES6. And it seems that the limitation now is not the stack of the particular environment but the Number.MAX_VALUE. As Douglas Crockford said: "JavaScript becomes a real functional programming language" with TCO. By the way, see my solution how can it be possible to implement TCO.

Mh, I wonder if maybe approving them in reversed order (I did the ruby version first, after all, but they are displayed as a stack, if you get what I mean) would help, but - anyway - now I forked it :)

It may also help approving the BBQ kata translation now, before I release the other one, I wonder.

And thanks again for your patience and support :)

Oh, and if you have nothing against it, I will green-light this kata once the translation is approved. You will still be able to edit it soon after and until at least 500 users complete it, IIRC.

Seems totally fine to me and again kudos for the finesse in your kata: the secret message in the description itself was quite classy :)

Forked, try approving that instead.

And apparently I can't unpublish it at all, bug reported.

Nah, once published you can only unpublish or publish it with changes; but I think now I nailed it: if you read the "diff" tab, it expected me to call it "method" again; I saved with that change, let's see if now it works (we'll edit it back to "function") later. For some reason I assume it compares it with the one it was once I started the translation.

If this does not work, I think I'll erase it and try copy&pasting it all again in a new translation.

Glad the other two went well, no need to feel at a fault for a technical error and at least on my side I am ready to try this as much as needed, don't worry :)

I have taken the current description and updated that of this (python) translation) accordingly and saved it, so, if you wish to try again to approve it, I think it should be fine.

[And just remember me a bit of fine tuning AFTER the approval ;)]

Thanks for the first one; I presume that it were the changes to the description that prevented the merge, so I copy%pasted the current description in the Python translation: see if now it is "approvable" to you.

On a side note: no need to put the language names over the code - we can see them all as we are editors, but a users only sees the language he has highlighted in the header. Anyway, don't remove what you changed before integrating the Python translation or I fear it will give you another error.

Thanks for your kind collaboration and your even kinder patience so far :)

Yeah; this is limited by the stack limit on recursion so it's not really valid for "all integers".

Thx. Fixed now.