Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Package file naming convention #16

Open
bcomnes opened this issue Feb 14, 2019 · 0 comments
Open

Package file naming convention #16

bcomnes opened this issue Feb 14, 2019 · 0 comments

Comments

@bcomnes
Copy link
Owner

bcomnes commented Feb 14, 2019

package file names (often) line up with with the name of a public export of the package
archive/tar has no tar/tar.go, but tar.NewWriter/tar.Writer comes out of tar/writer.go for example (edited)

i’d just pick at stblib packages if you want examples of the way to do it
https://github.com/golang/go/tree/master/src/bytes has bytes.go
https://github.com/golang/go/tree/master/src/archive/tar has no tar.go
no package has a file that contains all exports with other files that are only internal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant