i just came back to this kata, saw your comment, and read though the other solutions. Turns out, there wasn't a better way to do it lol.

That shouldn't make a difference? Array.Length is a property with O(1) constant lookup time.

I cannot believe this actually worked. The Python never ceases to amaze me

someone still gave this a "best practices" lmao

This language is literally pseudocode, I shouldn't be surprised by this

Wow, I used number theory in my solution, but it wasn't anywhere near this compact

done

C Translation (author inactive).

For the JS Kumite edge case test, please write to the console the numbers it actually testing for, instead of just writing "Edge Case"

wow... just wow

There's reinventing the wheel, and there's not knowing the wheel exists. Personally, I fall into the latter category

"TestsStringsUpTo40kLenForPerfomanceAssesment"

that was not very cash money of you

bruh

Better practice would be to declare an int equal to x.Length before the for loop and compare it to that, so x.Size only gets called once

Using a switch statement requires the data type to be an int, but hard converting a double to an int causes the decimal to be lost. OP multiplied by 10 and multiplied the ranges by 10 to circumnavigate that. Since input values only go to one decimal place, this works.