Double xforms feature flag & type aliasing approach#1
Open
Conversation
...and conversion traits.
General appraoch take was: - use chosen precision (as per flag) for cpu code - stick to 32bits for gpu code Also: - renames feature flag to "xform_64" to reduce typing for anyone `cargo check` ing both in the repo.
251f72f to
78e0a92
Compare
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
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.
.system(), part 4 (run criteria) ([Merged by Bors] - Optional.system(), part 4 (run criteria) bevyengine/bevy#2431)Commandsperformance ([Merged by Bors] - [ecs] ImproveCommandsperformance bevyengine/bevy#2332).system(), part 6 (chaining) ([Merged by Bors] - Optional.system(), part 6 (chaining) bevyengine/bevy#2494)get_insert_bundle_info([Merged by Bors] - moveget_insert_bundle_infobevyengine/bevy#2508)logcrate compatibility to bevy_logObjective
Solution