Hi Scott, > Should cyclic module dependencies be allowed?
Yes, indeed in some situations they are totally necessary. I wrote up an experience report on this very topic: https://gist.github.com/myitcv/79c3f12372e13b0cbbdf0411c8c46fd5 > Should a module, following a cycle, be able to depend on an earlier version > of itself? (I saw this once...) I can't see how this would work; indeed I can't even unravel it in my head! Do you have a concrete example to help explain? Thanks, Paul -- 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.
