4 ms·

Ah good, I've been waiting on a fix for one nasty bug in particular: https://github.com/golang/go/issues/3665 https://github.com/golang/go/issues/3665 I'm also

• jerf 11y ago
  The vendor support is that if you create a directory called "vendor" in the "current project", it will be preferred to the GOPATH for that project. That's pretty much it. The idea here is that they officially support that in the compiler, and then the community can build whatever tools it likes around that support. Whether you call that "support for vendoring" depends on exactly what you're looking for from "support". It's true that the compiler "supports" it, but it's also true that Go still has no "official" vendoring solution, unless you want to count the default one of manually mananging vendored directories, though I don't think most people interested in "vendoring" would call that support (and neither would I, so that's no criticism). I could use a tool that I could fire at a codebase that asserts that all imports are either coming out of the vendor directory or coming out of the base system.
• infogulch 11y ago
  Is that link right? You linked to a bug about http client support for Expect: 100-continue, and it looks like a fix was merged in October: https://github.com/golang/go/commit/dab143c8820151538fea908efe54e9625d1bc795 https://github.com/golang/go/commit/dab143c8820151538fea908e... Or are there still problems that aren't mentioned in that issue?
  • jcadam 11y ago
    Well, yes, but the fix won't be included until the 1.6 release.