Hi Igor,
The problem here is that in Go dependencies are linked to directories, not individual
files, several subpackages can ship files in the same directory (and Go mixing production
and unit test files in the same directory pretty much ensures the directory will need to
be split among subpackages), so a reliable way to tell "the autodep belongs to this
subpackage" or "this subpackage should not generate autodeps) is needed
Of course one can emulate this by mandating the Go directory should only be owned by one
subpackage, but that's awfully brittle and error-prone.
Regards,
--
Nicolas Mailhot