Why Rob Pike Opposes Adding Generics to Go 1.18’s Standard Library

Rob Pike, one of the founders of the Go language, posted issue #48918 on GitHub urging that generics should not be introduced into the Go 1.18 standard library and recommending that the standard library remain unchanged for now.

He gives two main reasons. First, the scope of the change is huge; Go 1.18 may include the largest language change since its inception—parameter polymorphism, commonly called generics. While the language itself has been evolving for over a decade, changes to the core libraries are very new and lack design experience, even though the Go team has done extensive work on the topic.

There is already extensive discussion about how the core libraries will adapt (see issues #45955, #48594, among others).

Second, there is a lack of practical experience. Using generics in the standard library requires careful planning, and adding them now would place a heavy burden on the release process.

Pike suggests testing generics in production through one or two development cycles, allowing the community to experiment in external repositories such as golang.org/x or golang.org/exp. Only after sufficient real‑world usage and experience are gathered should the standard library be updated.

Because the compatibility guarantees for generics make any mistake costly, the team prefers to wait, observe, and learn before proceeding.

In summary, Rob advises slowing down: “I realize everyone wants to enjoy the new language features, but I firmly believe it is best to proceed cautiously, learn, and act responsibly.”