On Friday, June 10, 2022 at 8:47:54 PM UTC-7 jlfo...@berkeley.edu wrote:
> > One hack solution I came up with to break cycles when Package A depends on > Package B which depends on Package A is to > create a symbolic link in Package A to the file(s) in Package B that > contain(s) the resources needed by Package A. Then Package A > wouldn't be dependent on Package B anymore, and the cycle will be broken. > (I just thought of this so I'm not 100% sure it will work > until I try it). > To follow up to myself, I wasn't thinking clearly. This idea obviously won't work. It's not what directory a file is in that determines what package it's is in. Rather, It's what's in its 'package' statement. Sorry for the noise. Jon -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/7dbe7f1a-c7fc-4f5f-8c66-eea0ed638c4an%40googlegroups.com.
