Probably because UUIDv4 is the most common type and is trivial to
approximate. For other requirements, there are non-RFC conformant
implementations that achieve the desired properties
On Wednesday, February 7, 2018 at 5:43:08 PM UTC-8, 高橋誠二 wrote:
> Recently satori/go.uuid took a breaking change of API, and some of
> frameworks which depend on the package.
> And google/uuid is unstable.
> Why Go doesn't have an official uuid package?
> Is there any load map to develop google/uuid and merge it to Go itself?
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.