-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
go get error #12
Comments
Yeah, unfortunately we're kind of stuck in a bad place until https://github.com/satori/go.uuid either tags a new release, or reverts the backwards incompatible changes to master (see satori/go.uuid#66 and satori/go.uuid#70). Here are some related issues and pull requests: #7 #8 #9 #10 #11 |
lithammer
pushed a commit
that referenced
this issue
Feb 14, 2018
Given the recent issues with github.com/satori/go.uuid (satori/go.uuid#66), which are still partly unresolved, e.g. its master isn't compatible with us (see #7, #8, #9, 10, #11 and #12). Even though github.com/google/uuid is only at v0.1 and clearly states this: >This package is currently in development and the API may not be stable. > >The API will become stable with v1. I suspect it's a better longterm investment.
lithammer
pushed a commit
that referenced
this issue
Feb 14, 2018
Given the recent issues with github.com/satori/go.uuid (satori/go.uuid#66), which are still partly unresolved, e.g. its master isn't compatible with us (see #7, #8, #9, 10, #11 and #12). Even though github.com/google/uuid is only at v0.1 and clearly states this: >This package is currently in development and the API may not be stable. > >The API will become stable with v1. I suspect it's a better longterm investment.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: