How do I split internal vs public packages in Go projects?

In Go projects, it's important to organize your code into internal and public packages to maintain encapsulation and promote code reuse. Internal packages are only accessible within a specific module, while public packages can be imported and used by other modules. This structure helps in managing dependencies effectively and ensures that your project's architecture is clear.

To split internal and public packages, you would typically create a directory called internal for your internal packages and organize your public packages in the root or other designated directories.

myproject/ ├── internal/ │ └── myinternalpkg/ │ └── myinternal.go ├── publicpkg/ │ └── mypublic.go └── main.go

Go Go packages internal packages public packages Go project structure Go modules

Related Questions

How do I avoid rehashing overhead with std::set in multithreaded code?

How do I find elements with custom comparators with std::set for embedded targets?

How do I erase elements while iterating with std::set for embedded targets?

How do I provide stable iteration order with std::unordered_map for large datasets?

How do I reserve capacity ahead of time with std::unordered_map for large datasets?

How do I erase elements while iterating with std::unordered_map in multithreaded code?

How do I provide stable iteration order with std::map for embedded targets?

How do I provide stable iteration order with std::map in multithreaded code?

How do I avoid rehashing overhead with std::map in performance-sensitive code?

How do I merge two containers efficiently with std::map for embedded targets?