Better generic bounds - #285
Merged
Merged
Conversation
…an oversight from the conversion to opaque masks.
… vectors can be combined back, and combined vectors can be split back
…elements, so that generic code doesn't accumulate extra bounds on every operation with them
LaurenzV
approved these changes
Jul 27, 2026
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.
The relationships that already hold for all types are now encoded in the type system, to allow more things to be expressed in generic code. Adds tests to enforce that this kind of generic code will keep compiling.
Unlike #284 this is not a breaking change because all the relevant traits are sealed (except SimdFrom but the change involving it is non-breaking).