The new type [KeepAliveConfig] permits fine-tuning the keep-alive
options for TCP connections, via a new [TCPConn.SetKeepAliveConfig]

<!-- go.dev/issue/64207 -->
As [announced](go1.22#darwin) in the Go 1.22 release notes,
Go 1.23 requires macOS 11 Big Sur or later;
support for previous versions has been discontinued.

### Wasm {#wasm}

<!-- go.dev/issue/63718 -->
The `go_wasip1_wasm_exec` script in `GOROOT/misc/wasm` has dropped support

pkg syscall (darwin-arm64), const NOTE_FFOR = 2147483648
pkg syscall (darwin-arm64), const NOTE_FFOR ideal-int
pkg syscall (darwin-arm64), const NOTE_FORK = 1073741824
pkg syscall (darwin-arm64), const NOTE_FORK ideal-int
pkg syscall (darwin-arm64), const NOTE_LEEWAY = 16
pkg syscall (darwin-arm64), const NOTE_LEEWAY ideal-int
pkg syscall (darwin-arm64), const NOTE_LINK = 16

pkg syscall (freebsd-arm64), const NOTE_FFOR = 2147483648
pkg syscall (freebsd-arm64), const NOTE_FFOR ideal-int
pkg syscall (freebsd-arm64), const NOTE_FORK = 1073741824
pkg syscall (freebsd-arm64), const NOTE_FORK ideal-int
pkg syscall (freebsd-arm64), const NOTE_LINK = 16
pkg syscall (freebsd-arm64), const NOTE_LINK ideal-int
pkg syscall (freebsd-arm64), const NOTE_LOWAT = 1

pkg syscall (linux-386), const PTRACE_EVENT_EXEC = 4
pkg syscall (linux-386), const PTRACE_EVENT_EXIT = 6
pkg syscall (linux-386), const PTRACE_EVENT_FORK = 1
pkg syscall (linux-386), const PTRACE_EVENT_VFORK = 2
pkg syscall (linux-386), const PTRACE_EVENT_VFORK_DONE = 5
pkg syscall (linux-386), const PTRACE_GETEVENTMSG = 16897
pkg syscall (linux-386), const PTRACE_GETFPREGS = 14

==============================

Before updating vendor directories, ensure that module mode is enabled.
Make sure that GO111MODULE is not set in the environment, or that it is
set to 'on' or 'auto', and if you use a go.work file, set GOWORK=off.

Requirements may be added, updated, and removed with 'go get'.
The vendor directory may be updated with 'go mod vendor'.
A typical sequence might be:

    cd src  # or src/cmd

pkg syscall (freebsd-riscv64), const NOTE_FFOR = 2147483648 #53466
pkg syscall (freebsd-riscv64), const NOTE_FFOR ideal-int #53466
pkg syscall (freebsd-riscv64), const NOTE_FORK = 1073741824 #53466
pkg syscall (freebsd-riscv64), const NOTE_FORK ideal-int #53466
pkg syscall (freebsd-riscv64), const NOTE_LINK = 16 #53466
pkg syscall (freebsd-riscv64), const NOTE_LINK ideal-int #53466

Using `panicnil=1` restores the behavior of Go 1.20 and earlier.

When compiling a work module or workspace that declares
an older Go version, the Go toolchain amends its defaults
to match that older Go version as closely as possible.
For example, when a Go 1.21 toolchain compiles a program,
if the work module's `go.mod` or the workspace's `go.work`
says `go` `1.20`, then the program defaults to `panicnil=1`,
matching Go 1.20 instead of Go 1.21.

The recommended way to file an issue is by running `go bug`.
Otherwise, when filing an issue, make sure to answer these five questions:

1. What version of Go are you using (`go version`)?
2. What operating system and processor architecture are you using?
3. What did you do?
4. What did you expect to see?
5. What did you see instead?

### New unique package

The new [unique](/pkg/unique) package provides facilities for
canonicalizing values (like "interning" or "hash-consing").

Any value of comparable type may be canonicalized with the new
`Make[T]` function, which produces a reference to a canonical copy of
the value in the form of a `Handle[T]`.
Two `Handle[T]` are equal if and only if the values used to produce the
handles are equal, allowing programs to deduplicate values and reduce