Thanks you for the translation. Approved.

Thanks you for the translation. Approved.

Got it, I think I misread the test code, thanks for clarifying.

Currently, the test suite is performing 100 random tests on lists that are loops approximately 50% of the time, which is standard for a Haskell kata. The input generation should produce an adequate amount of random inputs of varying lengths.

I can certainly increase the number of tests, but given the difficulty of the kata, I don't think that's necessary.

I don't know Haskell, but the number of test cases seem pretty low compared to the other languages. Is this fine?

Marking as resolved.

Thanks you for the translation. Approved.

LC translation

this translation modifies the description ( it adds a language-specific block )

approve Groovy and Haskell first

Now you have to approve it, or it's still not doing any good. ( Same for the other one. )

I've updated the description, to fix description merge conflict.

I've updated the description, to fix description merge conflict.

Thanks you for the translation. Approved.

I'm not sure that works. It might, but it might not.

Just fork all translations so they have the new description, and approve the forks. That definitely works.

Better to approve any translations you intend to approve, and only change the description in the editor ( or a translation! a translation can also change the description, and that also invalidates any other pending translations ) when none are pending.

If your reaction is "Huh? Wow.", yes, all of us think that.

Oh, sorry I didn't know about that. Should I revert the change, merge the translations, then add it back?

Thus invalidating all pending translations with a description merge conflict.

Related: have the tests stabilised, are all existing languages updated, and is the kata good to be approved now?