3 ms·

Maybe I'm missing something, but I think there is a need. If your code imports dependencies A & B and they depend on C at two different versions, how can you ha

Maybe I'm missing something, but I think there is a need. If your code imports dependencies A & B and they depend on C at two different versions, how can you handle this unless C is structured with versioned dirs?

atombender 5y ago
Go does not map the module path directly to a file system path. You can import v1 and v2 at the same time because they have different module names. In other words, this is allowed: $ go get github.com/linkedin/goavro@v1.0.5 $ go get github.com/linkedin/goavro/v2@v2.10.1 Then: $ go list -m ... | grep goavro github.com/linkedin/goavro v1.0.5 github.com/linkedin/goavro/v2 v2.10.1 Version 1 has a go.mod that declares: module github.com/linkedin/goavro and version 2 has a go.mod that declares: module github.com/linkedin/goavro/v2 but both have their Go files located in the root of the repository.