> 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. -- 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.
