I second Jan's request for light-shedding. It's one thing to add real indirect dependencies. I can sort of understand that. Can't think of a sensible reason for adding dependencies that are unrelated to the code in the module.
On Thursday, September 5, 2019 at 2:23:11 PM UTC-4, Jan Mercl wrote: > > On Thu, Sep 5, 2019 at 8:18 PM <mihaib...@gmail.com <javascript:>> wrote: > > > Running 'go get ...' inside a module can add indirect dependencies to > go.mod. > > I'm surprised. There's probably some rationale behind `go get` having > such side effects. Can anyone please shed some light on this? > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/5de47c75-79ea-429c-866f-5091c5210426%40googlegroups.com.
