614f2284d9
Go release notes always start out as a draft with a clear notice. That notice is removed when the final release (go1.N.0) is made. For example, the last time was in CL 562255. Add this to the Go 1.23 draft and to the future fragment template. Also switch to the main pkg.go.dev instance and use a relative issue link in 3-tools.md while here. For #64169. For #65614. Change-Id: I16bc0fa8a3a43ee7a9edd7fa253999041f1892e2 Reviewed-on: https://go-review.googlesource.com/c/go/+/587415 Reviewed-by: Jonathan Amsterdam <jba@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Bypass: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
1.1 KiB
Tools
Go command
Setting the GOROOT_FINAL environment variable no longer has an effect
(#62047).
Distributions that install the go command to a location other than
$GOROOT/bin/go should install a symlink instead of relocating
or copying the go binary.
The new go env -changed flag causes the command to print only
those settings whose effective value differs from the default value
that would be obtained in an empty environment with no prior uses of the -w flag.
Vet
The go vet subcommand now includes the
stdversion
analyzer, which flags references to symbols that are too new for the version
of Go in effect in the referring file. (The effective version is determined
by the go directive in the file's enclosing go.mod file, and
by any //go:build constraints
in the file.)
For example, it will report a diagnostic for a reference to the
reflect.TypeFor function (introduced in go1.22) from a file in a
module whose go.mod file specifies go 1.21.