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
API Changes #2
Comments
I think the text/template style of
|
Thank you for bringing that up again. Yes, it sort of go lost in the mix. I think it makes a lot of sense. Would you like to create a pull request to do this? The existing MustParse can just go away then. I would be happy to do it, but it would be nice for the history to show it came from you. |
Sure thing, #3 |
During those changes I noticed that the global variables don't seem to conform to Go best practices (e.g. code review wiki). In addition to use of underscores and CAPS (i.e. NIL) I think the capitalization of NameSpace is incorrect because namespace is a single word. It seems like the global variables should have the following names
|
@pborman any thoughts on the proposed name changes above? I've took a real pass through the API and came up with a couple other suggestions.
|
The name Nil is correct. From RFC 4122: 4.1.7. Nil UUID The other name changes look reasonable. |
I have push fixes for the naming issues, including a few others with non-exported names. |
Indeed that is my mistake about the Nil UUID. I didn't realize that name was part of the specification. |
Could there be a function to compare the equality of UUIDs? |
There is no need for a function, arrays (which is what the UUID type is) are directly comparable. |
Please comment in this issue about any requested API changes.
The text was updated successfully, but these errors were encountered: