Thanks!

How was this a "copyright infringement"?

It's possible to figure this out entirely on your own, without any real math background. I don't have one. I imagine googling would work too, although that takes the fun out of it.

Please don't copy and paste posts.

thanks! :)

IIRC I meant digits would go over 32-bits, not that you coudln't use bitwise operators for rounding.

The tests at the time were badly broken so I exploited them to point that out. All you had to do at the time was return true.

No it wasn't. Given this was 4 years ago, it's the earliest post pointing out random tests are needed.

At 100+ chars, literally anyone could get it. In fact at 63 chars just about anyone could do it. This is a golfing kata, meant to be a challenge.

Yeah, the description isn't clear (I didn't write it). I guess it should be changed to 5 specifically.

Possible I missed some edge cases. Regardless, your solution had numerous issues (including failing to round up from x.xxxx5), which is likely why it took you 100+ attempts.

I'm sure you could have found a more constructive way to phrase that, but updated.

As it happens, it looks like I didn't so much "make a mess", as the original JS solution had issues which were exposed by the additional tests-- something I didn't realize as my solution passed against the reference when I tried it.

Your solution, by the way, has a few issues with it.

Right; this meanas your solution isn't efficient enough (likely of the wrong complexity). You'll need to come up with a faster solution, which probably means rethinking it.

Random tests added, random decimals added.

Good lord.