Go 1.27 has shipped with three language spec changes: generic methods, struct literal keys via nested field selectors, and generalized function type inference across assignment contexts. The toolchain gains new go fix modernizers, versioned go doc queries, and automatic go mod tidy consolidation. Runtime improvements include size-specialized memory allocation cutting small-object allocation costs by up to 30% and a now-generally-available goroutineleak profile for detecting blocked goroutines. Standard library additions include encoding/json/v2, a post-quantum ML-DSA signature scheme in crypto/mldsa, a native uuid package, experimental SIMD support, and an in-memory fake network in net/http/httptest for use with testing/synctest.
Table of contents
Language changes ¶Tool improvements ¶Performance and runtime ¶Standard library additions ¶Questions this post answers
What are the new language changes in Go 1.27?
Go 1.27 adds three language spec changes: generic methods (e.g., a single generic Rand.N method replaces separate Int32N, Int64N, IntN methods), struct literal keys that can use any valid field selector to initialize nested or embedded struct fields directly, and generalized function type inference that now applies in all assignment contexts including composite literals, type conversions, and channel sends. Keep up with Go language changes like these as new versions ship on daily.dev.
What does encoding/json/v2 add in Go 1.27?
Go 1.27 introduces encoding/json/v2, which provides high-level JSON processing with configurable options and stricter defaults, alongside encoding/json/jsontext for low-level streaming. The existing encoding/json package is now backed by the v2 implementation internally, giving faster unmarshaling while keeping full backwards compatibility with existing code. Track standard library additions like json/v2 before upgrading Go services on daily.dev.
How much faster is memory allocation in Go 1.27?
Size-specialized memory allocation in Go 1.27 reduces small object allocation costs (under 80 bytes) by up to 30%, which translates to roughly a 1% overall performance improvement for allocation-heavy programs. Additionally, the goroutineleak profile in runtime/pprof is now generally available, enabling automatic detection of permanently blocked goroutines. Follow runtime and performance changes like this to plan Go upgrades on daily.dev.