Thanks you for the opinion. My colleagues are using satori/go.uuid, with web framework, "goa". API breaking change broke that package and our team had trouble for versioning. https://github.com/satori/go.uuid/issues/66
I know it is not the problem of the code of uuid generation itself, but my friends in other companies also had the same problem, or they create an original generator. it is just the reinventing the wheel so I asked why go has no standard uuid package. it's sure that defining the default format, but except for large-scaled system, generally you can be satisfied with a plain "securerandom" string, can't you? 2018年2月9日金曜日 11時10分52秒 UTC+9 Dave Cheney: > > But that’s the problem, who’s default uuid format is chosen? And how to > justify this over the other users who want their default to be chosen. > > The answer is as it currently stands, multiple uuid libraries exist > outside the standard library. > > Can you tell me, in concrete terms, what are the benefits to you of a (I’m > going to assume the one that is compatible with your project) uuid > implementation being included in the standard library. -- 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.
