Re: [go-nuts] Necessity of import constraints for golint

On 13 Oct 2018, at 00:57, Ian Lance Taylor mailto:i...@golang.org>> wrote: So, as a general rule, it's a good idea for any package to enforce that it is imported under a particular import path. I strongly disagree with this point. In my experience, import path comments are used to enforce the

Re: [go-nuts] Necessity of import constraints for golint

On Fri, Oct 12, 2018 at 11:29 AM, wrote: > > I was wondering if there's a particular reason to enforce importing golint > from a certain source (see: > https://github.com/golang/lint/commit/9a272034dedb2a3ed05231d5604ce17fb40f0e58). > There seems to be a lot of code in "the wild" importing this p

[go-nuts] Necessity of import constraints for golint

I was wondering if there's a particular reason to enforce importing golint from a certain source (see: https://github.com/golang/lint/commit/9a272034dedb2a3ed05231d5604ce17fb40f0e58). There seems to be a lot of code in "the wild" importing this project from github.com as evinced by a number of