-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Feature/glam cross constants #21561
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
pine-free
wants to merge
13
commits into
bevyengine:main
Choose a base branch
from
pine-free:feature/glam-cross-constants
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+158
−0
Open
Feature/glam cross constants #21561
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
cf4b1dd
add CARDINALS constant to Dir2 and Dir3
9b2e9e1
added the DIAGONALS const
c10d08f
added ALL_NEIGHBORS constant
35ab172
applied formatter to new changes
a913e2b
fix clippy warning about precision
003b605
updated the 1/sqrt(3) const to be in line with the unstable rust defi…
99986cc
added reason for allow of excessive precision
4be20e8
replaced allow with expect as per CI hint
ddf0d5a
formatting and typo fixes
91452e2
added ALL_EDGES group and fixed the ALL_NEIGHBORS to have all the nei…
pin3free f6c1789
fix documentation terminology for neighbors
pin3free 621263b
fix typos
pin3free a8f891d
Update crates/bevy_math/src/direction.rs
pine-free File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems a bit weird, since an f32 can't hold more than about 7 digits of precision, but I don't know if there's maybe another reason to want an extra-precise constant definition.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these excessively long definitions are copied from the rust std::f32::consts, but I'm unsure why they would be there in the first place
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i propose to keep this definition for now for the sake of consistency with the rust stdlib, so that when the FRAC_1_SQRT_3 gets stabilized we can just switch over to that and be certain that there's no weird behavior from unexpected changes