Hi all, I am wondering about cyclic dependencies w.r.t. modules. I haven't been able to find anything related, but also haven't verified all the possible related discussion venues, which would take a while.
Let me start out with an observation: Suppose module A has packages A A/x module B has packages B B/y It is possible for A to import B, and B/y to import A/x. This would not be a cycle in terms of package imports. But to my understanding, it would be a cycle in terms of module dependencies. Normally, I'd think that might be a bad idea. However, I have seen and used this pattern in order to facilitate testing, where it felt legitimate because at least one of the imports above was only for testing. So, some questions come to mind: Should cyclic module dependencies be allowed? Should a module, following a cycle, be able to depend on an earlier version of itself? (I saw this once...) Any ideas out there? Best, Scott -- 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.
