Of course, but it doesn't have to add 1 ... twice every time 😉

turning this to an exponent does not give you a string that is accurate. (trailing 0's where real numbers should be)

No fractional values now, but it still is called with Float64 arguments.

fixed

Crystal: the solution is called with floating point arguments that actually have fractional values.

Thanks :)

OP solved it, closing

Tests are not wrong, only your code is wrong for tests 2, 3, and 5.

Several of the fixed tests are wrong for python. no 2, 3 and either 5 all give me True should equal False

Love this one, so simple

My code provides the right output on my system yet it shows test case 2 and 3 failed with expected output [9,6] and showing mine output as [14,10] idk what i am doing wrong

Personally i find the way checks are made on original array to be extreamly frustrating. It makes error testing nearly impossible if that is your issue. That being said: love the kata. 10/10 other than that.

I would like to point out that 6 month to eight ago i reported the same issue only to have it immediately closed by someone being a troll. The actions of that person made it impossible for me to get advice from others or report things like this bug (they kept closing out all my bug reports) and its the reason i moved to other coding platforms than this to code.

hi,
303 total: 3 basic, 100 random and 200 big array (1000x1000) tests!
cheers