167 wires and counting

$ follow Go

Keep up with Go in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-06-10
stories 39

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

GO FIXES GENERIC METHOD BUGS ACROSS THE TOOLCHAIN

By RepoJournal · Filed · About Go · Composed from the cited sources · methodology

The tools team shipped a series of fixes for generic method handling that were causing silent failures in callgraph analysis and SSA instantiation.

Generic methods are getting proper support across Go's analysis tools after a week of targeted fixes. The RTA callgraph fingerprinting now skips generic methods correctly [1], static callgraph analysis gained generic method support [2], and a critical bug in SSA instantiation that was returning uninstantiated methods instead of monomorphized instances is fixed [3]. These changes resolve golang/go#77549 and affect anyone using static analysis, code generation, or IDE features that depend on accurate method resolution. On the compiler side, the Go team tightened range loop semantics by eliminating redundant length re-evaluations [4], fixing spurious nil checks that interfere with line number assignment. The encoding/json/v2 initiative continues to stabilize: the format tag is now available via runtime Option [5] instead of requiring compile-time flags, giving developers runtime flexibility without losing the opt-in safety of the v2 API. Documentation was updated to drop the format tag mention from v1 docs [6]. Security documentation landed a new set of decision guidelines covering what Go considers in-scope for security patches: excessive resource consumption (O(n^2) panics) [7], panic classification [8], attacker-controlled environments [9], and HTTP client redirect behavior [10].

Action items

References

  1. [1] go/callgraph/rta: skip generic methods in fingerprinting ↗ golang/tools
  2. [2] go/callgraph/static: support generic methods ↗ golang/tools
  3. [3] go/ssa: fix instantiation of generic methods on non-generic receivers ↗ golang/tools
  4. [4] cmd/compile: don't re-evaluate length of value being ranged over ↗ golang/go
  5. [5] encoding/json/v2: support format tag via runtime Option ↗ golang/go
  6. [6] encoding/json: drop documentation mention of `format` ↗ golang/go
  7. [7] _content/doc/security: decision: excessive resource consumption ↗ golang/website
  8. [8] _content/doc/security: decision: panics ↗ golang/website
  9. [9] _content/doc/security: decision: attacker-controlled environment ↗ golang/website
  10. [10] _content/doc/security: decision: HTTP client redirects ↗ golang/website

Quick answers

What shipped in Go on June 10, 2026?
The tools team shipped a series of fixes for generic method handling that were causing silent failures in callgraph analysis and SSA instantiation. In total, 39 commits landed.
What were the notable Go updates?
go/callgraph/rta: skip generic methods in fingerprinting, go/callgraph/static: support generic methods, and go/ssa: fix instantiation of generic methods on non-generic receivers.