As far as I understand the Toolchains document, Go projects made with Go 1.21 or later can demand a particular toolchain for compiling a module (through the go and toolchain directives). If you disable downloading toolchains as needed, the new behavior of the go and toolchain directives might break your workflow.
What prevents you from using the new toolchains mechanism? On Tuesday, August 15, 2023 at 8:39:43 AM UTC+2 Stephen Illingworth wrote: > With regards to the new Toolchain Management feature introduced in 1.21.0 > > Currently, my toolchain management is: download the source; compile; set > paths to point to the new version. I like this and it works for me. > > Am I correct in thinking that the environment variable, GOTOOLCHAIN=local, > will > disable the automatic downloading of new Go toolchains and allow me to > continue > with my current system? > > > I hope this isn't seen as a criticism of new developments. It's not meant > to be. > But I don't believe I'm in the target audience for this new feature and > want to > continue with my work as I am currently. > > Regards > Stephen > -- 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/b0bb8115-32df-4b43-a4f5-b7a879509c46n%40googlegroups.com.
