For Java, in your testcases, you may want to use assertArrayEquals instead of assertEquals

youre close to your given runtime but using arr1.sort() and arr2.sort() at the start ruins it - try arr1.reverse() and arr2.reverse() instead

This entirely defeats the point of the problem, that being to take advantage of the fact that the arrays are already sorted.

It's not actually a great solution because it requires a big dependency and uses floating point.

Bars, bars, bars ...

because he used 'i' and the first used 'x'

Hell yeah. Awsome backstory for a kata. Actually has a real world application. First time I ever put a switch statement in a for loop. Awsome and awsome.

Eva is actually closer to the original Hebrew.

python new test framework

well yeah, the "position" arguments are actually [y, x], not [x, y]

true

me not with typescript haha. Feels like getting more bad.

Not a kata issue. OP solved it, closing.

Not a kata issue.

Example: if you are on Ryu and move left, you must get to Guile; if you are on Balrog and move up, you must stay on Balrog.

Java fork, please review:

• move to JUnit 5
• change the imports
• annotate tests with @DisplayName and @Order
• remove a System.out.println leftover