Re: [go-nuts] single instance of package/mutex in a build?

[Robert Engels]

Yes, what Axel said is what I was referring to - with the last clause in the affirmative that I don’t consider them the same package. But using a stable third package to enforce a single instance works and is what I would do.  On May 11, 2025, at 3:23 AM, Jason E. Aten <j.e.a...@gmail.com> wrote: Thanks for the reply, Robert. I had thought, mistakenly that v1.6 and v1.7, of v0.8 and v1.0  might collide, and I was concerned about having multiple instances of a what should be a global mutex. But it turns out, when I tested this, and as Axel kindly pointed out, the module system will always upgrade or downgrade everything together _unless_ you have v2 vs v1 situation. It takes a major number difference to induce a two copy situation. I've tried to read RSC's article on Semantic Import Versioning, but I find it is vastly too long, and much too reliable a soporific. I'm thankful for Axel's salient summary and advice. -- 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 visit https://groups.google.com/d/msgid/golang-nuts/1d3dc715-54d5-4cf2-895b-695b76652379n%40googlegroups.com. -- 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 visit https://groups.google.com/d/msgid/golang-nuts/39793E31-3088-4766-92AC-B250C988459B%40ix.netcom.com.