Packages are handy for hiding implementation details of a given package from packages that use the given package. However, introducing a package currently has a downside: the package's externals become visible outside the module containing the package. If breaking changes are made to the package, its module's major version must be bumped. It would be nice to avoid this when a package is really intended to be an implementation detail of a module. If the package could be *hidden* from users of the module, breaking changes could then be made to the package without necessarily impacting other modules.
I'd be grateful for any pointers to previous discussions of this topic. There was no mention of similar features being deemed out of scope in the modules wiki <https://github.com/golang/go/wiki/Modules>. -- 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. For more options, visit https://groups.google.com/d/optout.
