Sorry, I used an incorrect example. The final user is supposed to be in module mode and even if in GOPATH mode, the latest version is still compatible with the old version.
On Sunday, May 16, 2021 at 4:04:38 PM UTC+2 Manlio Perillo wrote: > One example (not tested) is the case of a module X that depends on A and B. > A depends on an old version of github.com/speedata/hyphenation, and B > depends on a new version (that is compatible with the old version but has a > new API). > > In GOPATH mode, X can not be built. > > > Manlio > On Sunday, May 16, 2021 at 3:36:53 PM UTC+2 Patrick wrote: > >> OK, but what are the advantages for others? >> >> For my projects I use modules (locally) to have a list of dependencies >> with a checksum so builds could be reproducible. This works for remote >> packages with and without go.mod. What is the actual value for other users? >> Is this about versioning (semantic versioning)? Or is it easier to checksum? >> >> Thanks >> >> Patrick >> >> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/b698e9bc-b07b-441e-a95c-d40da680a658n%40googlegroups.com.
