You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Go 1.13 will use Go modules by default, so all Go packages should be updated to supporting Go modules. But it shouldn't only be done for the sake of adhering to the best practices / up-to-date tools in the Go ecosystem, but it's actually useful, too. Especially because there are so many gokv subpackages and almost all of them they have dependencies to third-party packages, and currently no dependency is pinned to a specific version in any way. Go modules allows pinning dependencies to specific versions, without the need to vendor their source code, but with checksums to make sure the dependencies haven't been tampered with when fetching them anew.
Go 1.13 will use Go modules by default, so all Go packages should be updated to supporting Go modules. But it shouldn't only be done for the sake of adhering to the best practices / up-to-date tools in the Go ecosystem, but it's actually useful, too. Especially because there are so many
gokv
subpackages and almost all of them they have dependencies to third-party packages, and currently no dependency is pinned to a specific version in any way. Go modules allows pinning dependencies to specific versions, without the need to vendor their source code, but with checksums to make sure the dependencies haven't been tampered with when fetching them anew.Useful links:
The text was updated successfully, but these errors were encountered: