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:
It's a scraper and i'm already planning to drastically reduce
implementations by grouping them into common ones that can be configured
but i will not be able to do it for all of them
Il giorno giovedì 16 febbraio 2017 17:14:34 UTC+1, Henry ha scritto:
>
> It's difficult to recommend any specific
Can you be more specific?
Il giorno giovedì 16 febbraio 2017 14:36:19 UTC+1, Henry ha scritto:
>
> It seems like you could use some serious refactoring there, rather than
> merely organizing your files.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts"
I'm developing a library where i have 1 common interface and a lot of
implementations (likely hundreds).
A single implementation is not too complex and can reside in a single
source file but then i have visibility issues with constants etc. Should i
just create a package for each implementation?
