Go 1.27 lets you delete code: generic methods, four go fix modernizers, a leak profile

Go 1.27 shipped with generic methods, four new go fix modernizers, and a generally available `goroutineleak` profile in `runtime/pprof` ^{[1][2][7][10]}. Each of those replaces work teams have been doing by hand, which makes this a release you act on rather than read about.

The clearest deletion is in Go's own standard library. Before 1.27, `math/rand/v2.Rand` needed a separate method per integer width, `Int32N`, `Int64N` and `IntN`, plus unsigned variants the release notes omitted for brevity ^[3]. Go 1.27 replaces the set with one generic method, `N[Int intType](n Int) Int` ^[3]. Any interface you shaped that way because methods could not take type parameters is now a candidate for collapsing. Two smaller changes cut boilerplate in the same direction: a struct literal key may now be any valid field selector, so fields in embedded or nested structs can be initialised directly ^[4], and function type inference has been generalised to all assignment contexts, so generic functions can be used without explicit type arguments in composite literals, type conversions and channel sends ^[5].

The new modernizers are `atomictypes`, `embedlit`, `slicesbackward` and `unsafefuncs` ^[6]. GoLand 2026.2 surfaces the same rewrites as editor inspections, collects every applicable one across a project in the Problems window, and applies them in bulk ^[20][24]. JetBrains has also added go fix as a pre-commit check that runs the modernizers and applies updates automatically, shipped disabled by default ^[23]. Disabled is the correct default; a hook that edits code at commit time is a policy decision. Worth noting that the JetBrains list of 1.27 modernizers names five categories, including generic iterator improvements and safer unsafe pointer arithmetic, where the release notes name four tools, so the mapping between the two lists is not stated publicly ^[21][22].

The leak profile is the part that belongs in CI. According to JetBrains, it reports goroutines permanently blocked because the synchronization primitive they are waiting on, a channel, `sync.Mutex` or `sync.Cond`, has become unreachable ^[11]. That criterion is narrower than "stuck": a goroutine blocked forever on a channel something still references does not qualify ^[12]. Because the profile lives in `runtime/pprof` rather than in an external agent, it can be captured in-process, the same way CPU and heap profiles are taken from a test binary ^[30]. GoLand 2026.2 captures and analyses it alongside CPU, memory, mutex, block and goroutine profiles, and can import a pprof file taken from a running production service ^[25][26].

The rest of the release is planning work, not deletion. Small object allocation under 80 bytes is up to 30% cheaper, worth about 1% overall on allocation-heavy programs ^[13]. `encoding/json` is now backed by the new v2 implementation, which the Go team says is faster at unmarshaling while staying backwards compatible, alongside a new `encoding/json/v2` and low-level `jsontext` ^[14]. `crypto/mldsa` adds FIPS 204 post-quantum signatures wired into `crypto/x509` and `crypto/tls` ^[15], there is a native `uuid` package ^[16], and `httptest.NewTestServer` provides an in-memory fake network for use with `testing/synctest` ^[19]. The `simd` packages remain experimental, with `archsimd` revising its AMD64 API and adding Arm Neon and WebAssembly 128-bit support ^[18]. Tooling also gains `go doc package@version` queries and a `go mod tidy` that consolidates multiple `require` blocks into a two-block structure ^[8][9].

Watch whether the unreachability criterion catches the leaks you actually have, which you learn only by pointing the profile at a service you know leaks ^[12]. Watch for behaviour drift where the v2 backing meets the compatibility promise ^[14]. And watch whether teams enable the pre-commit modernizer, since that decides if go fix is routine hygiene or a once-per-upgrade migration ^[23]. JetBrains says it has added Go 1.27 context to its Modern Go Code Guidelines so coding agents emit the same patterns ^[27]; an online release party with an overview from the Go development team, demos and Q&A is scheduled for August 25, 2026, 4:00 to 5:30 pm UTC ^[28].