I don’t think a Go program can have two different version of the same package. That is what go.mod ensures and why most (all?) Go builds require access to all source code. 

On May 10, 2025, at 11:45 PM, Jason E. Aten <j.e.a...@gmail.com> wrote:


Is there a way to insure I've only got one version
of a package in a build?  I need to make sure
a single mutex is used by all goroutines.

Detailed back story is here:
https://github.com/golang/go/issues/73665

--
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/bdc40509-6b71-469e-82ce-c5fb4a64211bn%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/DE2A8556-CA02-4C2F-BC98-BFB90C5F95C5%40ix.netcom.com.

Reply via email to