Hi Mike,
My understanding is that the folks operating the proxy have already removed
that:
"note that the module in question is no longer available from the
module proxy"
https://github.com/golang/go/issues/66653#issuecomment-2637831755
Best regards,
--thepudds
On Thursday, Feb
Hi Doug,
Consider this a drive by comment, but you might be able to create a version
of the nested module that does not have any code in it, and set up a
requirement cycle between the nested module and a new parent version.
I think there’s a general approach of creating a requirement cycle f
Hi Declan,
Virus scanners can slow things down significantly on Windows, including
virus scanners can go into overdrive if you are touching many files,
touching files with atypical extensions, or building and then immediately
executing a new binary.
To start, you could try temporarily disablin
Hi Pat,
FWIW, I pulled together a TLDR on modules some time ago that I think hits
upon each of the different issues you encountered in this thread. It also
tries to summarize the core modules concepts, along with a bit of advice on
how to stay on the "happy path" when starting out with Go modul
Hi there,
I might be misunderstanding your question, but a 'use' directive in a
go.work file points to a directory.
In your example, there would not be any ambiguity -- 'use ./hello' in a
go.work file would refer to whatever module you have located in the 'hello'
directory in your local files
Hello fellow gophers,
Ian announced the intention to update how type switches work in the
generics proposal in a golang-nuts thread from this August:
https://groups.google.com/g/golang-nuts/c/iAD0NBz3DYw
It included this from Ian (which is a snippet of his item #4 from his first
post ther
