If your project exposes one interface and many implementations of it then I'd consider it reasonable to have your interface in the top level package and a subpackage for each implementation.
On Fri, Feb 17, 2017, 02:33 Luca Looz <luca.loo...@gmail.com> wrote: > I'm starting now the project and i'm seeking advices on how to organize > packages. Should i use a separate package for each implementation to avoid > visibility issues with constants and other global vars that are internal > for only a single implementation? > > Il giorno venerdì 17 febbraio 2017 01:31:43 UTC+1, Henry ha scritto: > > Alternatively, you can leave them where they are and focus on the future > so that future implementation of the interface doesn't add to more garbage. > It may be possible to use fewer data types with configurable behavior. > > -- > 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. > -- 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.
