Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
Duplicate of any
zip
like kata. Here's a non-exhaustive list:The link at the end of the description links to a draft kata, and should be removed.
How about inputs like this (based on the python version):
etc... :-)
( JS, possibly others )
Description and example tests do not mention digits and uppercase at all and make a great show of keeping inputs simple ( no real parsing! no this, no that! ). Random tests suddenly have digits and uppercase.
It's legal, but it should be specified.
( JS, possibly others )
A
function
can do things that are utterly, completely inexpressible in fat arrow notation. The description tells us several things we will not encounter, but lots of things that can't be done in fat arrow notation are never mentioned. How would you likefunction error(_) { throw new Error; }
to be translated?Please specify that we will only encounter simple cases that can be rewritten rather mindlessly TBH, or, even better, specify what we will encounter. This should probably not be in the Notes section either.
Reraising issue:
Kata is a duplicate. See issue below for other comments.
In your fixed tests, you write that "Variant" should have only 2 syllables. Maybe I am crazy, but I am certain there is 3.
If you are defining 'syllables' in some other way, then you need to SPECIFY. If you aren't, then the reference solution is wrong (And likely, the kata would be MUCH more difficult if not impossible).
At the moment, this is essentially: "Guess the mystery function. Hint: it has something to do with vowels."
Please, provide a thorough explanation of what you do or don't consider a syllable.
And don't close issues without doing anything. The problem reported by Unnamed is still present, and telling people to "try submitting again" is not a solution to it.
I think this would be more interesting if you force the answer to be very robust. Randomize the number of spaces between things, add lambdas inside the lambdas, check edge cases where the name of the function is something like
lambda_f
, etc. Just my opinion though.Random tests always generate only a single word.
Trivial map/filter/reduce is not a novel idea.
no random tests
None
ifa == b
" requirement doesn't make any sensea > b
doesn't make this one novel or interesting