After some experiments I have decided that, for me, Go is a good substitute
for C and Python.
Since I writing some projects in Go I would like to choose one project
and stick with it.
Official go documentation only imposes one requirement on project layout:
it must be
This means that the layout used by the go compiler itself is no good.
I have these additional requirements:
1) The project top level directory must be clean; it must no contain source
code, but only project metadata (license, readme) and some
2) I'm very bad at choosing names, and since I also work in C and Python,
I want to be sure there are no possible name clash.
Currently I'm thinking to use the following layout:
- The package name is go.<prj> or go-<prj>.
I don't like go<prj>.
An alternate prefix is golang, but it is longer.
- There is no source code in the top level directory.
Go packages are in subdirectories.
This means one additional path element, but it should not be a problem.
- Commands go in the cmd subdirectory.
As an example:
foo package is imported as:
Feedback will be appreciated.
Thanks Manlio Perillo
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
For more options, visit https://groups.google.com/d/optout.