Go native vendoring (a.k.a. GO15VENDOREXPERIMENT) allows you to freeze dependencies by putting them in a vendor
folder in your project. The compiler will then look there before searching the GOPATH.
The only annoyance compared to using a per-project GOPATH, which is what we used to do, is that you might forget to vendor a package that you have in your GOPATH. The program will build for you, but it won't for anyone else. Back to the WFM times!
I decided I wanted something, a tool, to check that all my (non-stdlib) dependencies were vendored.
At first I thought of using go list
, which Dave Cheney appropriately called a swiss army knife, but while it can show the entire recursive dependency tree (format .Deps
), there's no way to know from the templating engine if a dependency is in the standard library.
We could just pass each output back into go list
to check for .Standard
, but I thought this would be a good occasion to build a very simple static analysis tool. Go's simplicity and libraries make it a very easy task, as you will see.
We use golang.org/x/tools/go/loader
to Continue reading
IPv6 is badly designed. Constant updates make us uncertain. Lack of features make us unwilling.
The post Blessay: IPv6 was Designed For Different Er appeared first on EtherealMind.
Texas Education Telecommunication Network announced the deployment of Noction Intelligent Routing platform in its Dallas PoP. The main purpose behind implementing Noction’s
The post TETN deploys Noction IRP to improve its commodity internet service appeared first on Noction.
Innovative enterprises are finding clever ways wireless technology can have significant business impact.