Add math.IsNearlyZero() and math.IsNearlyEqual() #2172
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These simple functions should be used when comparing numbers instead of
==
, since floating point precision issues easily arise.Felt like making them since someone on the Garry's Mod Discord server was confused as to why the following didn't work:
So now, you can use
math.IsNearlyEqual()
ormath.IsNearlyZero()
which solves the issue:The functions allow you to give them a tolerance of your choice, but they'll default to
math.exp( -8 )
otherwise.Additional reason why the function is needed:
It's more visible when you display the decimal values.