The [Func] type, which represents a function or method symbol, now
has a [Func.Signature] method that returns the function's type, which

## Ports {#ports}

### Darwin {#darwin}

<!-- 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

src/cmd/go.mod. When a package outside std or cmd is imported
by a package inside std or cmd, the import path is interpreted
as if it had a "vendor/" prefix. For example, within "crypto/tls",
an import of "golang.org/x/crypto/cryptobyte" resolves to
"vendor/golang.org/x/crypto/cryptobyte". When a package with the
same path is imported from a package outside std or cmd, it will

Unlike many projects on GitHub, the Go project does not use its bug tracker for general discussion or asking questions.
We only use our bug tracker for tracking bugs and tracking proposals going through the [Proposal Process](https://go.dev/s/proposal-process).

For asking questions, see:

* [The golang-nuts mailing list](https://groups.google.com/d/forum/golang-nuts)

* [The Go Forum](https://forum.golangbridge.org/), a web-based forum

pkg syscall (darwin-arm64), const BPF_MUL ideal-int
pkg syscall (darwin-arm64), const BPF_NEG = 128
pkg syscall (darwin-arm64), const BPF_NEG ideal-int
pkg syscall (darwin-arm64), const BPF_OR = 64
pkg syscall (darwin-arm64), const BPF_OR ideal-int
pkg syscall (darwin-arm64), const BPF_RELEASE = 199606
pkg syscall (darwin-arm64), const BPF_RELEASE ideal-int
pkg syscall (darwin-arm64), const BPF_RET = 6

pkg syscall (freebsd-arm64), const BPF_MUL ideal-int
pkg syscall (freebsd-arm64), const BPF_NEG = 128
pkg syscall (freebsd-arm64), const BPF_NEG ideal-int
pkg syscall (freebsd-arm64), const BPF_OR = 64
pkg syscall (freebsd-arm64), const BPF_OR ideal-int
pkg syscall (freebsd-arm64), const BPF_RELEASE = 199606
pkg syscall (freebsd-arm64), const BPF_RELEASE ideal-int
pkg syscall (freebsd-arm64), const BPF_RET = 6

they had fired and never collected unstopped `Ticker`s.

Second, the timer channel associated with a `Timer` or `Ticker` is
now unbuffered, with capacity 0.
The main effect of this change is that Go now guarantees
that for any call to a `Reset` or `Stop` method, no stale values
prepared before that call will be sent or received after the call.
Earlier versions of Go used channels with a one-element buffer,

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`,

The `initial` and `next` subdirectories of this directory are for release notes.

## For developers

Release notes should be added to `next` by editing existing files or creating
new files. **Do not add RELNOTE=yes comments in CLs.** Instead, add a file to
the CL (or ask the author to do so).

At the end of the development cycle, the files will be merged by being
concatenated in sorted order by pathname. Files in the directory matching the

## Before filing an issue

If you are unsure whether you have found a bug, please consider asking in the [golang-nuts mailing
list](https://groups.google.com/forum/#!forum/golang-nuts) or [other forums](https://golang.org/help/) first. If
the behavior you are seeing is confirmed as a bug or issue, it can easily be re-raised in the issue tracker.

## Filing issues