> First, my overall point is that I have decided to use only acyclic > dependencies, as cyclic ones are too complicated for me. > I don't feel easily convincible otherwise; that comes from a combination of > using go modules where some cycles crept in > and a strong bias for a dead simple dependency methodology.
That's totally fine, with the slight caveat being that in some cases they're unavoidable (e.g. the GopherJS case). I've drafted a guide that presents what I hope is a simpler example of a cyclic dependency: https://github.com/myitcv/go-modules-by-example/tree/013_cyclic/013_cyclic One point to note is that this example will become simpler still once https://github.com/golang/go/issues/26241 is resolved. Would appreciate any feedback, but please don't feel obliged. I fear it may take a few iterations to get the wording/emphasis right... 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.
