You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current comparison strategy math::equal is using primitive absolute magnitude comparison. This may not be sufficient in some cases, for example where relative magnitudes are large, or the values being compared border numerical precision boundaries.
Per @sherm1 recommendation in pull request #82, we should add math::numericallyEqual and math::relativelyEqual.
Also, see issue #42 for extension to Vector3 class.
The text was updated successfully, but these errors were encountered:
Original report (archived issue) by John Hsu (Bitbucket: hsu, GitHub: hsu).
Current comparison strategy math::equal is using primitive absolute magnitude comparison. This may not be sufficient in some cases, for example where relative magnitudes are large, or the values being compared border numerical precision boundaries.
Per @sherm1 recommendation in pull request #82, we should add
math::numericallyEqual
andmath::relativelyEqual
.Also, see issue #42 for extension to Vector3 class.
The text was updated successfully, but these errors were encountered: