@lisyarus Thanks a lot! This is one of my larger pet peeves. In the last 10 years I probably needed exact comparisons 95%+ of the time (if you exclude test code). And I mostly regretted any epsilon comparison in time. This is all with the exception of tests, where "approximate equal to the expected result" is fine.

But basically "load-bearing" comparisons with eps didn't bear any load in the end...

@lisyarus I had one client who had operator== on their Vector3 class overloaded with a non-zero epsilon.

Can you imagine how a std::unordered_map behaves if the equality operator might pick up the wrong element? That's fun to debug.