Go team explains why Go 1.27 allows type parameters on concrete methods but not interface methods

A Go blog post covers the reasoning behind generic methods, including the compiler limits that rule out generic interface methods.

In a post dated 26 August 2026, the Go team explains the language change in Go 1.27 that lets concrete methods declare their own type parameters. Until now, generic behaviour attached to a type had to be written as a package-level function.

The example is a generic linked list with a Map method that returns a list of a different element type. Written as a method, chained calls read left to right instead of inside out, and the helper stays scoped to the type rather than crowding the package.

The post also explains what is not changing. A generic method cannot satisfy an interface, and interfaces still cannot declare generic methods, because separately compiled packages would force the compiler to instantiate a method for every possible type argument.

Developers on Go 1.27 can use the feature to tidy helper APIs on their own types. Library authors should note that generic methods do not add new ways to implement interfaces.

Sources

• Generic Methodsofficial

Verified Oct 27, 2026 (official source). gogenericslanguagego1.27