On Sat, Nov 10, 2018, at 10:39, Paul Jolly wrote: > I don't think there's anything wrong with this distinction - when you > say "unless this has been fixed", are you suggesting the behaviour is > wrong or could be improved in some respect?
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. —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.
