4 ms·
Go seems very cool, but after watching many tutorials, attending a Google workshop for students on Go, and reading the docs, I'm still confused by how one is su
by dalanmiller 13y ago
Go seems very cool, but after watching many tutorials, attending a Google workshop for students on Go, and reading the docs, I'm still confused by how one is supposed to manage a Go project in the simplest way.
- cnbuff410 13y agohere is the simplest way to handle it: Just make your whole source code folder(or even your home folder) which contains all your projects to be gopath, and forget about it. Go can live peacefully with any other project.
- fauigerzigerk 13y agoThat's until you start thinking about dependency versioning. The only way I can think of how to integrate versioning into Go's "one workspace" philosophy is to encode versions into package paths and then use import aliases to point to different versions of packages. But that means you're spreading versioning information across all source files, and it only works if everyone decides to use this approach. So far no one does (I believe).
- dalanmiller 13y agoI think I will go with this method for the time being, thank you!