I feel uneasy a bit about tags (since they can come from anywhere/any-branch). But maybe that's just being over pessimistic, about handling/managing major versions.
And IDEs should use .mod files to reach for the source code of a definition - which is very helpful at development time. Now there are situations that I'm worried about that might damage the development experience - like when a package, five levels down is using an older major version of a certain package and our package is using the latest version of that certain package. On Monday, February 26, 2018 at 12:02:32 PM UTC+3:30, wilk wrote: > > On 26-02-2018, Kaveh Shahbazian wrote: > > > It would be nice if vgo could handle something like (in .mod files) > > `pkg > >>1.2.1 branch-name-*` and the `*` part could be a major number and the > > `1.2.1` is tag. The `branch-name-*` part is a pattern for branch name. > > If I understand what you mean, I would resolv this with replace > directive of go.mod to a clone of the branch. This clone could be > a subrepositories of the dvcs to can keep everything. > > -- > William > > -- 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.
