[Uid] use one class per type of UUID #36066
Merged
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.
(embeds #36064 for now)
Would it make sense to have one class per type of UUID?
This aligns the type system and UUID types, so that one could type hint e.g.
UuidV4 $uuid
.This PR does so.
UuidV1
/2/3/4 andNullUuid
all extend the baseUuid
class, which provides common methods and the factories needed to create each king of UUID.This means we don't need the
getType()
nor theisNull()
methods since they can be replaced by instanceof checks.As expected,
getTime()
andgetMac()
then now exist only on theUuidV1
class - no need for any version check nor anyLogicException
anymore.Each type is guaranteed to contain a UUID that matches its class' type. The base
Uuid
class is used for the "no type" type.