-
Notifications
You must be signed in to change notification settings - Fork 4
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 modules links #12
Comments
v2+ discussion:
• Putting major versions in import paths for v2+ modules could create incompatibilities with older versions of Go. To help with this, Go versions 1.9.7+ and 1.10.3+ have been updated so that code built with those releases can properly consume v2+ modules without requiring modification of pre-existing code. Happy to learn otherwise, or if there is a piece that could use clarification. |
https://github.com/marwan-at-work/mod Marwan Sulaiman [10:17 AM] |
golang/go#27009 (comment) v2+ confusion |
Dep complaints |
https://github.com/golang/go/wiki/Modules#semantic-import-versioning
thepudds [7:38 PM] |
Depreciating packages https://rakyll.org/deprecated/ |
Main: https://github.com/bcomnes/goref#vgo-go-modules-and-dependencies
Integrate these:
Paul Jolly [7:24 AM]
@thepudds to my knowledge, everything module-related should be accessible via
go help modules
, i.e. it's the starting point for the module journeySo your link above is spot on to my mind
https://tip.golang.org/cmd/go/#hdr-Pseudo_versions
https://github.com/golang/go/wiki/Modules
go get thing@version talk
golang/go#24250 (comment)
The text was updated successfully, but these errors were encountered: