> > You can, of course, create internal packages if you want to, but I'd see > that as completely unnecessary. You can just create an unexported type just > as well. >
But declaring an unexported type pollutes the package namespace, and that's what Josh is (understandably) trying to solve for (in part). > internal packages should be used sparsely. > Is there guidance on how/when they should be used? Would appreciate any pointers. -- 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.
