I have seen bugs that, essentially, were caused by a floating point less-than comparison. You can still get bitten if you're not careful. (A calculation was bei

I have seen bugs that, essentially, were caused by a floating point less-than comparison. You can still get bitten if you're not careful. (A calculation was being passed to acos(x), which is undefined for x > 1. In our case, mathematically, the inputs evaluated to exactly 1, but in the land of floating points, it was slightly off.) (The above bug is a restatement of bubblethink's sibling comment; it's an inequality where the two values are extremely (exactly!) close.) The Go bug on the lack of a round function had several broken implementations, none of which had a direct equality[1]. [1]: https://github.com/golang/go/issues/4594 https://github.com/golang/go/issues/4594