fix: float2 edge-edge intersection robustness #385
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes a false positive result in the edge–edge intersection test for non-intersecting, nearly collinear edges (#384). This fix primarily addresses `float2` precision issues (when using `double2` the issue was not detected). These checks will be improved in the future with *robust-predicates* implementation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes a false positive result in the edge–edge intersection test for non-intersecting, nearly collinear edges (#384). This fix primarily addresses
float2precision issues (when usingdouble2the issue was not detected). These checks will be improved in the future with robust-predicates implementation.