6 ms·

The toolchain management added in Go 1.21 sounds related to this. Hopefully you’re already aware of it, but if not, see https://go.dev/blog/toolchain https://go

The toolchain management added in Go 1.21 sounds related to this. Hopefully you’re already aware of it, but if not, see https://go.dev/blog/toolchain https://go.dev/blog/toolchain.

anttiharju 1y ago
It's a helpful link, thank you. I think I need to play with toolchain more. Last time I checked I think there was some corner case that was not covered but I could be wrong.
- anttiharju 1y ago
  With `brew install go` and module github.com/anttiharju/vmatch go 1.21.0 toolchain go1.21.1 I still get a binary that claims to be built with the latest version of Go instead of 1.21.1 or .0 vmatch has version 0.1.6+dirty built with go1.24.3 from 83c9aa83 on 2025-05-25T18:43:30Z I think this is a problem for me. Go 1.22 did a breaking change with the for loops for example https://go.dev/blog/loopvar-preview https://go.dev/blog/loopvar-preview. I see that I can change it with a command like `go env -w GOTOOLCHAIN=go1.21.1+auto` but then again I'm doing something I don't want, managing the version. Perhaps I'm missing some config.