This is clever as hell but far from a best practice in my opinion.

I added it. I couldn't find documentation for what I should put as the language name in the mark-down, so I assumed "fsharp".

Code looks great as usual but would you mind adding the F# function signature to the Kata description? Cheers :)

F# translation submitted, please review! :)

Yep, that was it :D Many thanks for your translation, reviewed and approved :)

My pleasure. If I understand your request correctly, all I needed to do was Edit, switch to the "Test Cases" tab and click "Publish"? I have done this. If you needed something different, please let me know.

Many thanks for taking the time to translate my Kata into F#. The code looks fine to me by eye but would you mind republishing this translation with the "Test Cases" tab on (i.e. Submit Tests) instead of the "Sample Test Cases"? I just want to be absolutely sure that the Submit tests are working as expected, cheers :)

Added a special random test for this case, so 1/3 of the solutions got invalid (one of your two solutions too);-)... Thanks for the hint!

You're welcome! The other katas in this series will also be receiving translations as I get time :)

Thanks for the clarification. I missed that part of the problem description. Perhaps we should add that as a static test, not just a random one?

This solution actually has the wrong precedence for the unary - operator. I managed to get it through by running until that random test did not generate. I am about to submit a new solution that addresses this issue.

Yes, higher... there is hint in the description: [hint: -2+2=0, but -2&2=-4 i.e. -2&2=-(2&2) and not (-2)&2]
Thanks for your work and solution;-)!

Many thanks for your contribution; reviewed and approved :D

I was only having fun :D Thats why they dont recommend linq and short hand if-else. They make it hard to read and debug.