54 bytes

why this kata is 7 kyu it's should be 8

Clever, but this code is less readable than if you split it into several functions with explicit names.

same. Even following along with the "video" the author describes, my solution passes around 30 per run.

the kata description already mentions this detail

I think the instruction is missing a rule for method beging 0 and the distance to the nearest number is equal in both directions.
It seems to be, that in that case, the smaller of both numbers should be chosen.

3 lines tho? :D :D quits

Approved. Thank you!

In my, highly personal, opinion, readability is actually better served by repeating test.assert_equals, and maintainability of simple code is better, even if you would have to patch the tests umpteen times to change something - but it's probably always the same change.

I prefer not having to read complicated code in some other place to fully interpret tests. And I have no limitless trust in authors not to introduce bugs in that code.

This might be worth discussing on Discord.

Haskell translation

this translation modifies the description

error[E0433]: failed to resolve: use of undeclared type `Road`
  --> src/lib.rs:81:39
   |
81 |             let mut road_simulation = Road::new(road, Car::init_position(road));
   |                                       ^^^^ use of undeclared type `Road`

error[E0433]: failed to resolve: use of undeclared type `Car`
  --> src/lib.rs:81:55
   |
81 |             let mut road_simulation = Road::new(road, Car::init_position(road));
   |                                                       ^^^ use of undeclared type `Car`

For more information about this error, try `rustc --explain E0433`.
error: could not compile `challenge` due to 2 previous errors


NOTE: Line numbers in error messages can be incorrect due to concatenation.

Thanks!

Pretty funny and quite simple kata to exercise with, well done.

javascript translation with attempt at making the description a bit more language agnostic

.