wow

arent you copying acc over and over ?

you should be dooing the length check first if length is a mismatch not to go through a possibly huge iterator

this doesnt seem to work on a calculator

make sure you put i < length instead of i <= length

@NikosEfthias: Not an issue if you can't produce reasoning for the issue.

@Valentin_Zuarez: you have solved the kata, in any case what you were probably trying to do is fixed.

https://en.wikipedia.org/wiki/Naming_convention_(programming)

Wtf, this should be in the description :/

Sorry for the inconvenience... The signature should have been:

let rec bouncing_ball = (h: float, bounce: float, window: float): int =>
  /* your code */
};

bouncing_ballinstead of bouncingBall.
Other guys passed the kata, silently modifying the name of the function.
Thanks!

reason code does not work bouncing_ball is not defined anywhere however the test suite tries to use that function

one or the other is used depending on the language

what does firstNumber/first_number even mean ?

I don't think hiding an error by returning an effectively random (words of length 0 don't exist) value is better than reporting an error, it will just result in an error somewhere else.

i think it would still be a better choise to do unwrap_or_default just to be safe

It's not even an optimization, it's the only logical choice.