On Sat, Nov 10, 2018, at 11:00, Paul Jolly wrote: > > I've just seen several projects do this wrong because they don't know about > > go mod tidy so they build, let CI run tests (and don't notice that the file > > has changed in CI), and call it a day never knowing that they're missing > > dependencies. Since I can't imagine why you'd want to have partial > > dependencies in the go.mod file (and even if you do, it's probably not > > nearly as common as wanting all of them), the default behavior of go build > > seems wrong to me. > > Equally, I'm not sure that I would expect a command that is subject to > build constraints to do something beyond those constraints, which is > exactly what would happen under such a proposal.
Maybe it's just me (and projects like the Stripe SDK and Blackfriday), but that's exactly what I would expect. Building source files is subject to build constraints, generating a go.mod isn't (or shouldn't be; unless there's some reason I'm missing why you'd want a go.mod file that's specific to an individual build with all its constraints?). —Sam -- 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.
