Updates to match bevy main #90
Closed
Conversation
This file contains 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
deontologician
changed the title
|
Closing this in favor of #91 which has a few more fixes |
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.
Currently, bevy main is on glam 0.15, and the released version of bevy (v0.5.0) on crates.io is on glam 0.13.
I'm imagining that
bevy_rapier/mastershould trackbevy/main, but maybe you like to go through and do all the changes after bevy actually makes a release. In any case, I figure whenever bevy pushes a new release, bevy_rapier will need to make this change one way or another, so here it is.(For context, I read through the discord/github issues and I understand the current recommendation is to add nalgebra with the
convert-glam015feature if someone is using bevy main.)