lint has import path checking: https://github.com/golang/lint/commit/9a272034dedb2a3ed05231d5604ce17fb40f0e58 …
"go get http://github.com/golang/lint/golint …" will now fail.
"go get http://golang.org/x/lint/golint " is the new hotness.
#golang
-
-
Replying to @dgryski
just got bit by this, all builds started failing :/ Import path restrictions are fine, but... adding them to an already-mature project is going to break stuff. Was there any forewarning?
1 reply 0 retweets 1 like -
Replying to @lukechampine
AFAICT, the README was updated in Feb : https://github.com/golang/lint/commit/ead987a65e5c7e053cf9633f9eac1f734f6b4fe3 … by
@andybons . I guess that's as much as there was.0 replies 0 retweets 0 likes -
what if (whispers into mic) you just didn’t use vanity import paths
1 reply 0 retweets 4 likes
I'm torn. I like that they remove dependence on a specific service like GitHub/GitLab. But I don't like atomizing the ecosystem and making users responsible for keeping their vanity server online.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.