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-11-01
stories 1

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

encoding/json/v2 trims redundant buffer stores

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

A single commit in golang/go introduces a CommitBuffer helper that removes redundant pointer stores and their associated write barriers from the jsontext and encoding/json/v2 encoders, a micro-optimization with no API change for callers.

encoding/json/jsontext, encoding/json/v2: avoid redundant buffer stores golang/go

by Jake Bailey

Jake Bailey's change adds CommitBuffer, which publishes an appended slice by reslicing the encoder buffer when it retains the backing array and storing the returned slice otherwise. Applied at the existing post-append buffer updates in jsontext and the default marshalers, it targets pointer stores and write barriers rather than allocation counts; the benchmark cited is a single run on linux/amd...

Quick answers

What shipped in Go on November 1, 2026?
A single commit in golang/go introduces a CommitBuffer helper that removes redundant pointer stores and their associated write barriers from the jsontext and encoding/json/v2 encoders, a micro-optimization with no API change for callers. In total, 1 commits landed.
Who contributed to Go on November 1, 2026?
1 developer shipped this update, including Jake Bailey.
What were the notable Go updates?
encoding/json/jsontext, encoding/json/v2: avoid redundant buffer stores.