I'm the F# and OCaml translator, so any suggestions for those could be tossed my way. :)

That's a good criticism; I was "following along" with the Javascript translation and didn't think to check how the Haskell translation worked.

That being said, I found that having the signature as a list actually made my solution simpler. Although I suppose that's subjective ;)

Yeah; I accidentally clicked "Javascript" once in the dropdown list, and no matter how many times I remove Javascript as a language for this kata, it won't seem to let me. I might have to just translate it into Javascript. :(

Thanks for the translation! I like the use of random tests; I'll have to dig into writing some of my own.

Thanks! I had a typo: (fun_ -> instead of (fun _ ->, causing my lambda not to be seen as such.

Whoops, good call. I was going through transcribing the Ocaml.org's "99 problems", and didn't think to check for overlap.

Added an OCaml translation: https://www.codewars.com/kumite/57dd4ef4f6df9b254400374c?sel=57dd4ef4f6df9b254400374c

Can do! I'm new to translating kata, so I'm still learning the etiquette.

I've been dipping my toes into translations since contributing OCaml/F# support so that hopefully other folks have stuff to do in either of those two languages.

Relatedly, I've got an F# translation of this too.

Ah, forgot to update the example cases after fixing the actual cases.

The Typescript version of this test has errors; the "reference" syntax at the top is wrong. It should be

<reference path="..." />

not

<reference path="..." ></reference>

I can fix it in the visible test cases, but when I go to submit, I'm hosed.

UndorderedList -> "UnorderedList"

At least in the Haskell version, I suggest having (visible, non-solution) test cases that verify the "wrap around" behavior.

I added these to my own tests when working this kata:

	it "should wrap around to the left" $ do
  	  cycleList L [1,2,3] 1 `shouldBe` Just 3
    
	it "should wrap around to the right" $ do
  	  cycleList R [1,2,3] 3 `shouldBe` Just 1