I agree. It seems to be based on having quite specific information about the structure of the package path based on the service it references. For instance, I

I agree. It seems to be based on having quite specific information about the structure of the package path based on the service it references. For instance, I assume that github.com/user/v2 will refer to version 0 or 1 of the 'v2' repository. When I wrote my own vgo-inspired package manager[0] I changed the handling of major versions in package paths such that they are separated by an @-sign. While github.com/user/v2@v3 still looks silly, I think it is less confusing. [0]: https://futhark.readthedocs.io/en/latest/package-management.html https://futhark.readthedocs.io/en/latest/package-management....