Allow passing a custom epsilon to is_equal_approx() and is_zero_approx() #104408
+418
−348
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.
Potential implementation for godotengine/godot-proposals#4425
This needs default arguments so its rebased off of #95017. So it needs that merged in first.
This effectively allows
is_zero_approx
to optionally receive a custom epsilon - allowing backwards compat.And also adds
is_equal_approx_custom_epsilon
(surely we can improve this name) binding, that is basically an alternative tois_equal_approx
if programmers wants to specify their own epsilon.Example usage:


Doc changes:


is_equal_approx()
andis_zero_approx()
godot-proposals#4425.