On Thu, Nov 15, 2018 at 1:38 AM Victor Giordano <vitucho3...@gmail.com> wrote:
example.com/foo can import example.com/bar: siblings vs "parent" and "child". example.com/foo can import example.com/foo/a but in the same time example.com/b can import example.com: "parent" and "child" meaning can be inverted or not. The conclusion is that there are no "parent"/"child" packages or "subpackages". Just packages that import other packages. It's true that the dependency graph must be a tree (acyclic), but that tree is independent of the import path hierarchy. -- -j -- 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.
