fix: less invasive solve_character_collision_impulses function#652
Merged
sebcrozet merged 2 commits intodimforge:masterfrom Jun 23, 2024
Merged
Conversation
This was referenced Jun 12, 2024
Taking ownership of the elements is not necessary. It also conveys the information that elements are only read.
92d31b9 to
980bfa6
Compare
sebcrozet
approved these changes
Jun 23, 2024
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
2 participants
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.
in
solve_character_collision_impulses, Taking ownership of theCharacterCollisionis not necessary, it's a problem if we're storing theCharacterCollisions in another struct, such as dimforge/bevy_rapier#523.This pull request would help avoid a copy of the
CharacterCollision.Using a reference is compatible with an owned
Vecand also conveys the information that elements are only read.