On: Taking Go modules for a spin

[codezero]

I’m no expert, and I might even be very wrong, but I read the post about it and it seems to hinge on only resolving a minimum version and assuming all future packages with the same import path are backwards compatible. If I’m reading right it basically treats path/to/package and path/to/package/v2 as entiresly different packages.

[eikenberry → codezero]

You are correct. It bakes semantic versioning into the dependency system making it a requirement vs. just a convention.