Small Vector Ergonomics Issue #39
Merged
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
maplant
changed the title
maplant
changed the title
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.
This changes the default representation of small (N = 2, 3, 4) vectors to be fixed structs, allowing the fields of the vector to be made more readily accessible.
I think this is nice, it provides a good balance between "here are practical things you need for making a game" to "here is a very broad set of matrix operations for any size".
One thing that I have not done is to implement operations between column vectors and vectors yet, which I think would be cool so that there are two implementations for a lot of common implementations, a fast one and an obviously correct one. Would be great for testing when I start converting some of these to SIMD