The problem with that is that Go has no support for a package that imports something from one package and re-exports it, so if you put things in two packages, you are in the general case requiring users to import two packages now.<p>Another one of those things that makes sense to me at scale, as I&#x27;ve been bitten before in the dynamic languages by excessively complicated re-exporting systems, but locally is sometimes annoying.