Chapter 8 Generics on Go: Under the Hood

8.1 The Evolution of Generics Design

Mon, 01 Jan 0001 00:00:00 +0000

8.1 The Evolution of Generics Design

Generics is the feature Go waited longest for, argued about most fiercely, and that best embodies its design philosophy. From the open-source release in 2009 to its arrival in Go 1.18 in 2022, the thirteen years of hesitation and the eventual choices are themselves a lesson in language design. This section answers three questions: why Go held off on generics for so long, how it finally added them, and how they are implemented underneath. The last question matters most, because Go’s implementation copies no existing precedent and instead takes a distinctive middle road, and it is that road that is Go’s real answer to the thirteen-year problem. How the design itself evolved along the way (contracts, type sets, several rounds of syntax proposals) is left to 8.4; this section takes only the skeleton.

8.2 Contract-Based Generics

Mon, 01 Jan 0001 00:00:00 +0000

8.2 Contract-Based Generics

This section has a companion online talk: on YouTube, Google Slides deck. The deck was recorded in 2019, while the contracts proposal was still under discussion, and it corroborates this section.

8.1 glossed over the evolution “contracts came first, then a turn toward interfaces as constraints” in a single sentence. This section unfolds that sentence: what contracts actually looked like, how much expressive power they had, and why they were ultimately abandoned. This rejected design is not historical waste; it explains where today’s [T Ordered] syntax came from, and it illustrates a move that recurs throughout Go’s design: first produce a highly expressive but somewhat complex scheme, then turn back and ask “can this be expressed with concepts we already have”, forcing complexity to earn its right to exist.

8.3 Type-Checking Techniques

Mon, 01 Jan 0001 00:00:00 +0000

8.3 Type-Checking Techniques

Generics pose a far harder problem to the type checker than before. The old judgment had only one shape: “is this value of this type?” With type parameters, the checker now has to answer three new questions: whether a type argument satisfies a constraint, whether an operation like a + b is valid on an unknown type, and what that unwritten T actually is when you call Max(3, 5). These three concerns correspond to the three topics of this section: type sets, core types, and type inference. They are where the design from 8.1 lands as concrete compile-time technique, and they are also a prelude to the front end of 15 The Compiler.

8.4 The Future of Generics

Mon, 01 Jan 0001 00:00:00 +0000

8.4 The Future of Generics

Generics landed in 1.18 and more than four years have passed. This section no longer dwells on speculation about “what might be.” Instead it looks back and takes inventory: which expectations were met, which were deliberately shelved, and where the tension that runs through it all (the cost of abstraction) stands today. The author once gave a public talk on Go 2 generics in earlier years (YouTube, slides). Most of those predictions can now be checked against reality, and this section accounts for them along the way.