See title - it’s a very simple FR!
Comparing floating point values to each other is potentially problematic, and so == and != on a Vector3D will also be problematic. It would only be suitable for specific cases such as comparing to (0, 0, 0).
It’s a perfectly valid request in my experience. Besides, this is why JUCE provides exactlyEqual and approximatelyEqual. Treating floating points vals like some untouchable, museum piece isn’t a good idea.
I’d rather this than have to consume glm and use vec3.