Repeated characters are to be ignored and non-alphebetic characters as well.
There should be fixed tests for that and currently, at least for javascript, the control function fails for a string with numbers in it (currently, not tested).
Returning inconsistent datatypes is not a best practice. Also, it is undefined if a non-empty string with only non-alphabetic characters is to return null or {}.
Merged.
CoffeeScript translation
There should be fixed tests for that and currently, at least for javascript, the control function fails for a string with numbers in it (currently, not tested).
Updated JavaScript
nice kata
Approved!
Python update (new testing framework)
my brain can't handle the creativity i had to use to not use the
keys
method ;pThere should be fixed tests with non-alphabetical strings to prevent solutions doing
{... for char_ in input_string if ...} or None
This comment is hidden because it contains spoiler information about the solution
duplicate issue
Aliasing a built-in is a worthless practice.
Haskell : https://www.codewars.com/kumite/5be8d9782635535c1b000113?sel=5be8d9782635535c1b000113
(the data type use is a very basic form of hash/lookup table for Haskell)
Took me actually longer figuring out what to do than writing the solution...
Returning inconsistent datatypes is not a best practice. Also, it is undefined if a non-empty string with only non-alphabetic characters is to return
null
or{}
.The JavaScript description uses non-JS language.
Not satisfied. :/
Loading more items...