On 15 December 2016 at 04:38, roger peppe <rogpe...@gmail.com> wrote: > > In my experience it is very common for circular dependencies to arise > not because > of something in a package that I'm using directly, but because of > something semi-related that > happens to sit in the same package. >
That's a good point. If I had a million dollars for each time someone at Google adds a dependency on a massive package just to get at one little function within it... -- 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.
