-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
proposal: crypto/uuid: add API to generate and parse UUID #62026
Comments
Note that this has been asked -and rejected- in the past, here: #23789, and here #28324. It's not clear what concrete, tangible benefits would bringing github.com/google/uuid in the standard library give us. Third-party packages are easy to import and use, and can have a more flexible release cycle than the standard library. |
Guess the strongest argument is going to be that if you have to import it externally every time, it might as well be part of the standard library in the first place. Pretty much every other language does, and tends to include it as part of its crypto library. |
UUID versions 1, 2, 3, 4, 5 are already outdated. The latest and most promising version is 7. See https://datatracker.ietf.org/doc/draft-ietf-uuidrev-rfc4122bis/ However, version 7 allows for many different implementation options. It is necessary to wait for the results of applying various options.
|
I would like to suggest the addition to the standard library of a package to generate and parse UUID identifiers, specifically versions 3, 4 and 5.
The main reason I see to include it is that the most popular 3rd-party package (github.com/google/uuid) is a staple import in every server/db based Go program, as confirmed by a quick Github code search.
Additionally:
Addendum
Would like to point out how Go is rather the exception than the norm with regards to including UUID support in its standard library.
The text was updated successfully, but these errors were encountered: