Whats a good best practice with Go workspaces?

Question

I\'m just getting into learning Go, and reading through existing code to learn \"how others are doing it\". In doing so, the use of a go \"workspace\", especially as it relates

Answer 1

At my company I created Virtualgo to make managing multiple GOPATHs super easy. A couple of advantages over handling it manually are:

• Automatic switching to the correct GOPATH when you cd to a project.
• It integrates well with vendoring tools
• It also sets the new GOBIN in your path, so you can use the executables installed there.
• It still has your original GOPATH as a backup. If a package is not found in the project specific workspace it will search the main GOPATH.