@jcsahnwaldt, seems like there's no progress anymore :(

Hmm, I would like the solution to be efficient also.
Maybe we could add that to the description?
I think the test that call stack is actually exceeded was a good one, since it eliminates a lot of the cheat solutions. Then the difficulty of this kata might also increase a bit :)

What do you think?

btw, do you know if tagging users do actually notify them?

Let's just keep that test case removed for now.

It's a good question. I would maybe say that if the solution can't handle a limit betweeen 20k and 50k, then it isn't good enough?

I don't know what's best.

@jcsahnwaldt, I added an additional test case, that expects the function to throw maximum call stack size error when called with a huge limit. I think that would catch some of the cheat solutions, but that test could also be easy to check by throwing an exception if limit is greater than a specific number. Anyways it doesn't hurt to have it :)

Thank you very much!!!

Nice, that's great!

I can live with this, you have to know the preloaded code to know that I use Error.captureStackTrace. And these hacks are IMO as hard as the actual solution :)

I marked your comments as spoilers, even though we fixed the ways to hack it, the comments might help others find new hacks :)

Nice :)

Looks good!

That's great, then I guess that the cheats we didn't catch are allowed :)

Ha, was just about to edit the kata, and then saw that you made the exact same change :)

Thanks, should be fixed now :) Check the preloaded code.

Cool, hope to get some more votes soon :)