Golang

0 readers

1 users here now

This is a community dedicated to the go programming language.

Useful Links:

Rules:

Posts must be relevant to Go
No NSFW content
No hate speech, bigotry, etc
Try to keep discussions on topic
No spam of tools/companies/advertisements
It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

founded 1 year ago

MODERATORS

Ategon@programming.dev

austin@programming.dev

RandomDevOpsDude@programming.dev

Is there a repository of best practices when it comes to Go? (project/file structure, decoupling) (programming.dev)

submitted 1 year ago by pillow@programming.dev to c/golang@programming.dev

10 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] CodeBlooded@programming.dev 5 points 1 year ago* (last edited 1 year ago) (1 children)

Apparently this repo is NOT any sort of standard, yet a lot of people are fooled to believe that based on the repo’s account name and the project’s name. I see this mentioned whenever this is asked… just an FYI…

[–] foehammer@programming.dev 3 points 1 year ago (1 children)

Some aspects of that repo are actually language features, such as the pkg and internal directories.

[–] CodeBlooded@programming.dev 2 points 1 year ago (1 children)

pkg/ isn't a language feature. It's just a popular convention that used to be used in the Go standard library.

[–] foehammer@programming.dev 1 points 1 year ago (1 children)

The language feature is the internal/ directory, and it's function of restricting dependencies from external programs.

[–] CodeBlooded@programming.dev 2 points 1 year ago

That is correct, internal/ is a feature. I was just clarifying that the pkg/ folder isn’t any sort of language feature as you had said it was.