Visual Studio Code for Go

Re:Visual Studio Code for Go by jzelinskie on Friday March 04, 2016 @12:26AM (#11222192)

I have a single $GOPATH per project and always recommend doing so. If you vendor code with a tool like godep[0], having one shared $GOPATH is a nightmare. Other tools might work better, but this is basically the standard for the projects I work on. I basically just have a zsh alias[1] that combines z[2] and sets the $GOPATH to $PWD split on "src". I do share a single $GOBIN set to $HOME/bin, though.

[0]: https://github.com/tools/godep

[1]: https://github.com/jzelinskie/dotfiles/blob/04ad026f30782189...

[2]: https://github.com/rupa/z

[ Parent | on HN ]

Re:Visual Studio Code for Go by KyleBrandt on Friday March 04, 2016 @10:13AM (#11224215)

Using govendor with my stuff and a shared GOPATH. I haven't noticed an issue, I wonder what makes it a nightmare for you?

[ Parent | on HN ]

Re:Visual Studio Code for Go by nulltype on Friday March 04, 2016 @03:57AM (#11222730)

I have a similar setup, but I actually alias the go command itself so I don't have to type anything special.

[ Parent | on HN ]