I have no idea, but in some Haskell katas we have helpful logs. The problem is that, from what I know, it's impossible to print the arguments in Haskell; with logs like this one the kata becomes almost impracticable.
Incidentally, I have solved this kata with no problem in all other currently available languages, my code in Haskell is absolutely similar, it uses the same methods I have used successfully in several others. I suspect tests are actually bad (kata solved only 12 times in hs), but it's impossible to check it.
I think it's a general problem with QuickCheck and it does not allow for neat, custom assertion messages, right?
Or does it?
Log tests are unusable in Haskell:
Falsifiable (after 2 tests):
's' expected 0 but got 1
We should be given, neatly, the input strings and the expected output.
Missing return type in Typescript initial solution
^And how does it being an old kata makes it 6 Kyu?
This comment is hidden because it contains spoiler information about the solution
I don’t understand why many kata creators think that we are here to solve puzzles, and not to solve programming problems.
I get the following error message, as I using more-itertools to solve this Kata:
Traceback (most recent call last):
File "main.py", line 1, in <module>
from solution import *
File "/home/codewarrior/solution.py", line 3, in <module>
import more_itertools as mit
ModuleNotFoundError: No module named 'more_itertools'
Is it not possible to use the more-itertools library?
I like to leave a positive comment if the kata is good, or write similar comments if the kata is not very good.