Native Polygon Intersection#37
Merged
Cleptomania merged 1 commit intodevelopmentfrom Mar 2, 2024
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This duplicates the
are_polygons_intersectingfunction essentially to have a "native" version which accepts a reference to the polygon points, which means that we do not need to clone the points when calling from with the SpriteList collision functions.The other way of not accepting references is still necessary for the function which is exposed to Python, but we can leverage the native version within the rust code to avoid the unnecessary data copying, gives roughly a couple percent improvement to the overall collision detection performance because that is an incredibly hot loop. to be doing copies in.