I've always argued that a package's name is a one word elevator pitch for what it provides--not what it contains.
Package models fails this tests because it enumerates the contents of the package. You could argue that this also provides the models for your project, but think about what happens when your models package and a models package from another part of your program need to be imported in the same package. In this situation my advice is to rename the models package, models.go and move the file into the package that relies on it. Dave -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
