Your argument that the stdlib grows a uuid package is really a call for stability. “3rd parties cannot provide us the stability we need, so the go team must”. I don’t think that is a fair expectation on the go team, especially as there is no clear standard for what a uuid is (having multiple inplemebtations pushes the discussion into the domain of the python standard library).
I think your problems would be best solved by forking the uuid library at a revision that works for you, or sponsoring the development of a sufficiently stable uuid library. There is clearly a market for one. -- 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.
