Converting to an array and using the every function also fails no loop test, and it's unclear what exactly "no loops" and "no recursion" mean, since they weren't detailed in the instructions or previewed in the sample tests.
This is a frustrating kata indeed. And the complexity doesn't come from solving the issue but finding a solution that fits all the guidelines, which aren't discovered until the failed test messages are given.Please consider either mentioning the requisites in the actual problem description or refactoring "Anti-cheat" section.
Dang I made the misstake of reading the discourse before trying to solve it. Got me scared shonkless of that last test. Should have just solved it first.
Looks like you forfeited by now since the code shown to me is the top voted one and I cannot find a solution of yours.
But I assume that you used some global variables somewhere, e.g. a "recursion counter" or something.
I have a problem with the testing closures. My code passed all tests, but I have an error in testing closures. I am confused, if my code works, why is it not passing testing closures. Could someone please help me.
I'm getting weird results, trying a recursive function with javascript:
expected 'I am very very very very very very very very happy and I am big and I am tall' to equal 'I am very very very very happy and I am very very very very very very very big and I am very very very very very tall'
Artifical requirements make the Kata much more frustrating than it needs to be, but not necessarily more challenging or rewarding
As @akar-0 mentioned, the checks against recursion in the submissions tests aren't mentioned anywhere in the description, nor are they present in the sample tests
The check against recursion is too weak and can easily be bypassed by changing the name of the recursive function (see my solution)
The best course of action is probably to drop the no loops / no recursion requirement altogether.
That's... an interesting way to think of it.
Converting to an array and using the every function also fails no loop test, and it's unclear what exactly "no loops" and "no recursion" mean, since they weren't detailed in the instructions or previewed in the sample tests.
Your kata has already been sent back to draft, closing...
This is a frustrating kata indeed. And the complexity doesn't come from solving the issue but finding a solution that fits all the guidelines, which aren't discovered until the failed test messages are given.Please consider either mentioning the requisites in the actual problem description or refactoring "Anti-cheat" section.
This comment is hidden because it contains spoiler information about the solution
CoffeeScript translation
Dang I made the misstake of reading the discourse before trying to solve it. Got me scared shonkless of that last test. Should have just solved it first.
Your solution is incorrect - not a kata issue.
Looks like you forfeited by now since the code shown to me is the top voted one and I cannot find a solution of yours.
But I assume that you used some global variables somewhere, e.g. a "recursion counter" or something.
hello,
I have a problem with the testing closures. My code passed all tests, but I have an error in testing closures. I am confused, if my code works, why is it not passing testing closures. Could someone please help me.
I'm getting weird results, trying a recursive function with javascript:
idk what to do!
Updated Python translation
The best course of action is probably to drop the no loops / no recursion requirement altogether.
Loading more items...