4 ms·
When you run `go get` and import packages from a remote Git or Mercurial repository. At least that's what Go docs call it[1]. [1]: https://golang.org/doc/code.
by cledet 11y ago
When you run `go get` and import packages from a remote Git or Mercurial repository. At least that's what Go docs call it[1].
[1]: https://golang.org/doc/code.html#remote https://golang.org/doc/code.html#remote
- nulltype 11y agoIf by "same side effects" you mean multiple versions of the same library causing issues, I don't think so. Using "go get" you will end up with only a single version of a library for a given path.
- cledet 11y agoAlmost, I mean you can only use a single version at a given time. An example would be if an imported library and its importer uses the same dependencies but one used an older API.
- nulltype 11y agoI think that is solved by the vendor thing. You can have two versions of the dependency, e.g. "vendor/dependency" and "vendor/library/vendor/dependency" and, with the caveats mentioned elsewhere (global name conflicts, similar-looking but different types, etc) it should work fine.