On Tuesday, 21 January 2020 11:04:28 UTC, Orson Cart wrote: > > I guess I'm looking for something like opaque pointers which were employed > to good effect in C to hide implementation details from 'peer' source > files: https://en.wikipedia.org/wiki/Opaque_pointer#C > > You can hide implementation details from peer source *packages*. You probably want to break your code up into smaller packages anyway: see https://blog.golang.org/package-names especially the section under "Bad package names"
A package which contains an 'internal' subdirectory can contain other sub-packages which are not exported: this may also be useful to you. <https://docs.google.com/document/d/1e8kOo3r51b2BWtTs_1uADIA5djfXhPT36s6eHVRIvaU/edit> https://golang.org/doc/go1.4#internalpackages -- 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 golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/9f46b981-dfc9-44ff-95ae-eb937cc8175c%40googlegroups.com.
