I felt a bit taken back by this aswell, and was the part i struggled the most with. It just doesn't feel very clean.

I used trial division and it was too slow, but then i looked for other factors in my code to improve the execution time, and was able to greatly reduce the excecution time. As a somewhat spoiler free hint, i thnk that memoization was a big factor for making it, mine in particular, faster.

Approved, thanks! 🖖

I forked your translation; added the fixed tests and made some minor corrections with the method name. You can approve my fork; you still get the honor for being the original translator.

EDIT: I went ahead and approved it. Thanks for the translation!

i've translated the test generator from the JS version. Please have a look over it.

I'll need some time to look this over. It would've made more sense to implement a function that generated random tests; while plentiful, those additional tests are still fixed tests.

In any case, I'll see about adding a random test generator to this kumite.

Added a bunch more tests based on the randomly generated tests of the JS version.

C# Translation published.

You are correct. There is a bug in the C# translation. I've asked the translator to fix it. Thanks for reporting!

I am talking about C#. Sorry, i should have stated that.

And in my original Java Kata, it is just like you thought it should be...

  @Test
  public void emptyZoo() {    
    final String input = "";
    final String[] expected = {
      "", 
      ""
    };
    assertArrayEquals(expected, Dinglemouse.whoEatsWho(input));
  }

Which language are you referring to where this is not the case? It might be a bug in a translation.
Thanks

i was a bit confused with the output section of this kata. given an empty input, i expected the expected output would be two empty strings - the tests, however, only expect one empty strign to be returned if an empty string is given as input.
IMO this could use with a touch up ;)