On Tuesday, May 10, 2022 at 12:19:57 PM UTC+8 Amnon wrote:
> OT, but why do you want to support the Go 1.15 toolchain? > 1.15 and 1.16 are no longer supported upstream, so will not get essential > security fixes. > Why not just ask your users to upgrade to 1.18.1? > I can recommend but not force them to use a recent version. And this is not a 1.15/1.16 specific problem. > > On Tuesday, 10 May 2022 at 01:24:12 UTC+1 tapi...@gmail.com wrote: > >> On Tuesday, May 10, 2022 at 1:46:35 AM UTC+8 Ian Lance Taylor wrote: >> >>> On Mon, May 9, 2022 at 10:18 AM tapi...@gmail.com <tapi...@gmail.com> >>> wrote: >>> > >>> > I have a project using go1.16 embedding feature. >>> > The project supports Go toolchain 1.15, by using "//go:build !go1.16" >>> directive. >>> > >>> > Now I have upgraded the toolchain to v1.18.1, >>> > And I want to debug the non-embedding flow of the project. >>> > Changing the go version in go.mod doesn't help. >>> > >>> > Do I have to install back Go toolchain 1.15? >>> >>> I don't think that what you want to do is supported. I recommend that >>> you install 1.15 somewhere. >>> >>> That said, you could try "go build -gcflags=-lang=go1.15". >>> >>> Ian >>> >> >> "go build -gcflags=-lang=go1.15" doesn't work too. >> OK, I will try to install 1.15 alongside. >> > -- 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/dc3fb718-6adb-479f-b545-6fe17f937fden%40googlegroups.com.
