Clever, but who is voting this as a best practice?! If I saw something this unreadable in a production codebase I'd be pissed.
Should use const instead of let for both.
Python and Ruby forks available, then.
Description cannot be approved, recent changes from related record must be merged first. (both Python and Ruby)
Same here for the Python and Ruby versions, cheers!
Any progress approving Python and Ruby versions as well :D?
I would like to propose this kata soon to some of my guys, you know ;)...
Awful documentation on what happens when a ascii > 255...
Needs more tests and random test cases. Also seemed to be a bit easy for a 6kyu ranking.
This doesn't check that there is an opening parens or that the other characters are digits.
Oops, forgot to approve, doh! Done now.
Regarding functional programming - thanks for the tip; I try and use it as much as possible, but my brain is still adjusting to using it in some situations.
Any problem approving them?
For functional programming, give a look at other solutions and you should get it, as it is very popular around codewarriors.
Thanks for adding the translations! And using a functional programming style is definitely something I'm working on :)
Python, Ruby and Crystal translations kumited; thanks for the another good kata; you might wish to adopt a more functional style of programming (instead of looping and pushing, for example), but otherwise nothing to object