Go: Bindings Without C Compiler, HTTP Proxy Fix
Go development is dominated by a push for C bindings that build without a C compiler, alongside an HTTP fix for non-chunked transfer encoding and a narrowed split debug default on Darwin.
Duration: PT2M10S
Episode overview
This episode is a short developer briefing from Go.
It explains recent repository work in plain language.
- Show: Go
- Published: 2026-11-21T14:06:35Z
- Audio duration: PT2M10S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning, it is Saturday, November twenty-first, twenty twenty-six, and this is your Go briefing.
The headline is a sustained push to let Go programs bind to C libraries without a C compiler, with a separate but important fix for HTTP reverse proxies.
The bindings work dominates the activity. Multiple changes from Michael Matloob wire the build command to recognize a new bindings mode, where files that import C are included only if they declare binding pragmas for functions, variables, types and dynamic loading. Once detected, the C G O tool generates Go wrappers…
Second, HTTP handling. Pull request eighty-three two fifty-two corrects response reading when transfer encoding ends in something other than chunked. Under R F C ninety-one twelve, that body runs until close and overrides content length. Previously it was rejected as unsupported, causing reverse proxies to return a…
Finally, on Apple platforms, the linker now enables split debug info by default only for plug-ins and C shared libraries, after reports of friction for executables.
What is next to watch is stabilization of the bindings experiment and whether the HTTP change backports. This is your Go briefing, signing off.
Nearby episodes from Go
- SIMD Simplification and Stdlib Hardening
- Deadlock Fixes, Float Rounding, and SIMD Gains
- Double-Rounding Fixes and Printer Safety
- Runtime Goes Native, Vector Fixes, Template Security Patch
- Vectors Become Comparable, Text Paths Get Faster
- Weekly Recap - Leaner Compiler, Reliable Wasm and HTTP Simplification
- Wasm Reliability and Runtime Cleanup
- HTTP Pool Unification and Compiler Efficiency