$ the-wire · showcase
Go tooling gets lossless float constants, split DWARF lands on Darwin
By RepoJournal · Filed · About Go · Composed from the cited sources · methodology
The day's work runs from a protocol bump that lets compiled constants round-trip exactly, to Darwin binaries gaining split DWARF, to pkgsite refusing cache payloads it could never have stored.
internal/gcimporter: encode float constants exactly in iexport golang/tools
The iexport protocol moves to v4 to encode float constants in one of three formats chosen by the constant.Value representation: 512-bit-mantissa binary floats as before, plus multiprecision integers and rationals. Alan Donovan's change lets constants like 1.0/3 round-trip without loss, and the encoding is never more than one tag byte longer than before, often shorter.
cmd/link: enable split DWARF by default on Darwin golang/go
Cherry Mui turned split DWARF on by default for Darwin now that the go command supports it, closing the long-standing request in golang/go#62577 and adding a linker test. A companion change emits .debug_aranges for Mach-O MH_DSYM files, because LLDB relies on it alone and does not fall back to scanning .debug_info, effectively undoing the earlier removal of that section.
internal/middleware: drop payloads that exceed maxCachePayloadBytes golang/pkgsite
Ethan Lee made the middleware drop payloads above the roughly 1MB Redis limit instead of attempting them. These were never cached and previously timed out, so the change reports the hit rate staying the same while cutting "context deadline exceeded" errors and the dead sockets they left in the connection pool.
Revert "runtime: throw if unswept spans remain in finishsweep_m" golang/go
Michael Pratt reverted the runtime check that threw when unswept spans remained in finishsweep_m. gcStart sweeps remaining spans before taking work.startSema, but if another GC races it for that lock, edge cases let finishsweep_m still observe unswept spans, so the assertion was unsound.
devtools/docker, tests/search: mount gomodcache in allbash and optimize search runner golang/pkgsite
The pkgsite dev tooling mounts the gomodcache named volume in the allbash service so modules survive across container runs, and makes the database host port configurable through GO_DISCOVERY_DATABASE_PORT (default 5432), which gets developers running a native PostgreSQL on the standard port out of conflict.
internal/postgres: favor module counts golang/pkgsite
The quieter pkgsite work points the same direction as the new search responses: importer counts are shifting toward modules rather than packages, because module counts lag far behind and are headed for the main package page.