result and my returned value equal but did not passed wtf?

Hello there. Would you be able to revise your Clojure translation, as there are multiple issues about it implying it's broken? Thanks.

approved

This fork adds them.

Yes please (see my answer in Discourse).

If something dubious in the translation had appeared to him no doubt he would have vigourously told me.

Then I expect it was a mechanical update without looking. It is really poor! No judgement to you but it needs changing if performance is to be tested at all, and the code itself deserves a bit of refactoring because it has some questionable things that cancel out.

To approve the translation I think you should/could find somebody who very well knows Haskell.

I don't know who I dare try drag into this. Perhaps someone catches this on the front page ..

I am very surpised not to see something in the "Output" panel.

I see output in the non-edit/published version of the kumite, and I see output when I run it. I also tried GHC 8.2 just for the sake of it and that runs green too.

know the ropes

an idiom meaning something along the lines of knowing the job, where things are how things work

Hi.
So err uhm. No clue what I'm doing. But. I think you might be the haskell translator for this kata, and I created an issue for it a week ago.
I also took a stab at improving the test code, here: https://www.codewars.com/kumite/568d26406fc5df24f8000029?sel=600ee1b619c04400080aeca4
I can edit it directly but tbh it should be under supervision since I do not know the ropes (please treat it with suspicion).

Many solutions will not pass these tests. This is VERY intentional, and in the spirit of the kata - see my issue.

Uhm. Actually the random tests look super wrong to me. I didn't pay much attention to them because it's just refactored from the original (which are then also super wrong if my refactoring is correct, idk)
...anyway, I'm leaving it at least until you reply.

... looking at the generated test cases, they're actually not as bad as I thought (I expected all True cases but it turns out to generate both) and I think my refactoring is probably correct and I blame it all on you :^). It might not be doing what is intended, the current code for those tests are using frequency in a pointless way .... anyhow, yeah, leaving it for the moment

Added

He couldn't get it to work on the root

I meant that one, the one that is over a week.

He couldn't get it to work on the root, so let's wait till these forks are a week old so he can try these.

I'll message B4B on gitter.

Yeah, we could ask someone else to try.
Did you try in Edge? I remember on the github convo you said things worked in Edge...
Also you could look in the console and see what kind of error is coming out

Maybe this is something related to your user again? Did you see https://github.com/codewars/codewars.com/issues/2017#issuecomment-607512316 ?