nothing compiles any more! i seem to be being forced to add, to some projects 9 years old (unnecessary) module support, or, add notes to all their docs that they need to be compiled in versions older than 1.16, or have to have an obscure parameter set.
there really wasn't a non-breaking way to do this? seems to me this has effectively become part of the language and should be implemented in accordance with the go1 backward compat. guarantee. what difference does it make to a user when things stop compiling like this. On Tuesday, 16 February 2021 at 19:56:37 UTC Alex Rakoczy wrote: > Hello gophers, > > We just released Go 1.16 > > To find out what has changed in Go 1.16, read the release notes: > https://golang.org/doc/go1.16 > > You can download binary and source distributions from our download page: > https://golang.org/dl/ > > If you have Go installed already, an easy way to try go1.16 > is by using the go command: > $ go get golang.org/dl/go1.16 > $ go1.16 download > > To compile from source using a Git clone, update to the release with > "git checkout go1.16" and build as usual. > > Thanks to everyone who contributed to the release! > > Cheers, > Alex and Dmitri for the Go Team > -- 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/da9d75a9-ba86-4ed6-ade4-bd80b7908176n%40googlegroups.com.
