Thanks for the approval; I changed the assignments to use single-assignment form from the kata editor. Also disabled Function, which I had forgotten

For what it's worth, I was vaguely familiar with what combinators were before I started this kata so I ended up having to manually derive most of the combinators from scratch (although the derived answers I got were extremely ugly and took me 2 weeks total), yet I loved the experience cause it really helped me understand combinators properly.

It doesn't lead to a stable sort though. The quicksort should do better there. But it's slower. It also depends on compare instead of le, which for eg. Church is less efficient.

Nice!

Approved

Well that seems kind of hard to debug in this case XD. Thanks for the tips.

Because 0 time coffees are only generated in JS I will try to remove them.

Hello, thanks for your tips and kind words related to the kata. Printing the random input test cases can be done by the warrior himself, so I thought that it was not really necessary to print them in case the warrior fails them. About the 0 time coffees, they are mentioned in the next challange in this kata series. Cheers.

C error has been fixed

Python (original language), COBOL and PHP don't generate zero values. JS does, Haskell I don' know. About C, I think there's an error and coffees[i] = rand() % 40 % 1; would rather be coffees[i] = rand() % 40 + 1;. Currently random tests generate zeros only arrays in this language.

COBOL and C tests print the input in case of failure.

I like your solution: It is very logical.

I published a fork where I tried to fix up the issues in the description. The main problem is that you need to use haskell and javascript instead of hs and js.

Have a look and make sure I didnt make an error somewhere in editing the description. Feel free to fork off that and make further changes if you want, you may also want to update the test framework to use the Mocha instead.

0 may strictly be outside the xorshift32 domain, but the shifting algorithm in general allows it, and it's a somewhat probable edge case for solutions. I'd put it in. Explicitly specify it's a valid input if you need to.

Single bit numbers - good idea!