Clever, but wrong. It would permit lat as 90.50 or long as -180.3; parsing should consider the whole number with optional fractional part, but that doesnt seem to be tested in validation.

Ahhhh, okay thanks, my mistake, I completely missed the x, y meaning.

Thanks for the response, so looking into the default test cases for the kata at line 45-48 it sets
up a new Blob instance and do a single move(), looking into the hardcoded expected result it lists
that [8,3,4] goes to [7,4,4] and not to [9,4,4] as should be expected by the example I gave above.

Is this test expected result wrong?

Regarding the second group of tests in the given test cases, on the upper right side of the initial grid it gives:

x x 1 x x
3 x x x 3
x x x x x
x x x x x
6 x x 4 x

I believe that both 3s count as distance 3 from the 4, so the priority rule should kick in.
Now the test says that the 4 moves toward the left 3, but according to the clock rule this
is roughly 10-h position while the right one if kinda 1-h position.
So which 3 should be the correct target? Or is my distance assumption wrong?