Why would that be a mistake? Working with tags and branches is what the VCS is for. Extracting a given version and using that per the convention that the import ends with the major version sounds very reasonable.
On Wed, Feb 21, 2018, 22:51 Zellyn <zel...@gmail.com> wrote: > On Wednesday, February 21, 2018 at 4:45:25 PM UTC-5, Bakul Shah wrote: >> >> Something like >> import "foo" v2 >> would be mildly preferable to me as >> import "foo/v2" >> can also refer to version 1 of a package named v2 (as opposed >> to version 2 of foo) and the current naming rules continue to >> work. >> > > As I understood it, the fundamental philosophical point of today's rsc > article was that you shouldn't use the the same "name" (identifier) for two > different "things". If you look at it from that point of view, the "v2" > should absolutely be part of the package URL. In fact, having the concept > of version stored in some lookaside metadata outside of the name (eg. git > tag) would be a mistake. > > Zellyn > > -- > 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. > For more options, visit https://groups.google.com/d/optout. > -- 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. For more options, visit https://groups.google.com/d/optout.
