Same here, would be helpful to have it explicitly stated in the directions just to save some time
I tried a solution with the incriment ++ operator (and no addition + operator) but it was rejected for using a +. So, apparently ++ isn't allowed either.
In Preloaded. Fork a solution and you can see it.
How did you define "usercode" in your tests to check the solution for the symbols and function?
Using other ways would make this kata at most a high 7kyu, so I had to kill them ;-)
Just my opinion:
The new and improved anti-cheat tests have killed all the different, creative solutions.
What you have done may actually very well be in the spirit of the kata as originally intended by its author, but, as you might know, I always enjoy seeing different solutions.
I do not consider this an improvement. :/
Prohibiting "." is pretty clever BTW. :]
That was a mistake, should be '.
I just added a check to Array as well, but then, since I've banned . it should be impossible to do anything with an array anyway.
The anti-cheat test rejected my comment below, claiming it looked like I was doing something with an array / object
Edit: Oops - didn't notice the .
new Array is not the [ or ] operator. The description should be clarified.
Edit: Also apparently the description says ; can't be used but clearly solutions are using it?
I also significantly ramped up the anti-cheat tests. All unintended solutions have been invalidated as far as I can see, so I think it's good to go ;-)
Not an issue ;-)