That's not a general solution.
(And if you know what you are doing, you can also compare floats exactly in some circumstances.)
But the article already mentions that.
(And if you know what you are doing, you can also compare floats exactly in some circumstances.)
But the article already mentions that.
In the process my coworker and found something we believed to be a bug with complex nans in some recent GCC versions, but where not smart enough to understand whether it is actually a bug or undefined behaviour in the standart.
Anyway, we where so exhausted from the refactor, we didn't follow it up again.
I knew what I was doing and that is why using Epsilon was the most reliable thing in my data processing algos.
Obviously, you need to account for tolerances, but that accounting does not need to be via an epsilon in your count, it can also take the form of careful numerical analysis. For example, in some numerical algorithms, it is right and proper to run them until an equality test (without epsilon) succeeds. And using any positive epsilon would give a worse result.