This was originally in Haskell, tho. Look at the language list, the one at the top is always the oldest. Tbh entire kata should be retired for garbageness.

Apparently this is resolved by latest JS fork.

this is what happens when you let a javascript programmer make a kata. this is normal levels of bullshit in javascript, therefore they think they can do it in katas. i wish i was kidding. katas with behaviour like this keep showing up, and it's always originally made in js.

It's ambiguous. IMO, it should return ["123"]. It says to return the last element, not the last element of the last element.

Kata needs clarification IMO.

...

You can always forfeit instead of solving.

You could harden it such that you figure out which IP is greatest and swap the subtraction, but I believe the challenge rules laid out rules about the expectations.

but why would start ip > ending ip ?

You can easily set the place of each argument before calling the method.

Updated the description

it doesn't have random tests :(

Thank you for explanation :)

Thanks!

Fixed.

It would probably not qualify as 8kyu anymore ;-)