I don't think UUID representation (whether with dash or without dash or how many dashes) is a strong argument for not including UUID into Go's stdlib. You can expose it in byte array, provide the default implementation for its string representation, and let the users work with the byte array if they need a custom string representation. By the way, the RFC did define the standard UUID string representation which is in the form of 8-4-4-4-12 (xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx) that you can use as the default UUID string representation.
That being said. It is also fairly trivial to implement your own UUID library. It takes a bit of reading to ensure your implementation conforms to the RFC. I know because I ended up implementing my own UUID library because there weren't such libraries back then. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
