feat: add Generic conformance for UUID and Date#9
Merged
Conversation
72d6643 to
9aec95b
Compare
JaapWijnen
reviewed
Dec 15, 2025
9aec95b to
782908c
Compare
JaapWijnen
approved these changes
Dec 15, 2025
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.
Summary
Adds (unboxed) Generic protocol conformance for UUID and Date.
UUIDuses aSIMD16<UInt8>raw representation, which matches the internaluuid_ttype of a 16-wide tuple. I also triedUInt128(macOS 15+) orSIMD2<UInt64>, but when loading the values (for copying in-out of the array) Swift/LLVM is smart enough to just do so as a singleSIMD2<UInt64>in all cases.Dategoes via the time interval since reference date so should be a no-op.