July 31, 2026
Settle down: Go found its sets
Golang proposal: container/: generic collection types
Go finally gets basic data buckets, and the crowd is cheering, roasting, and asking why it took so long
TLDR: Go plans to add long-missing built-in collection tools like sets and ordered maps, a big quality-of-life upgrade for developers. The community reaction is half applause, half roast: people are glad it’s happening, but many are asking why such basic features took this long and whether Go’s generic system is still awkward.
After years of telling developers to make do with the basics, Go is finally preparing to add a proper lineup of built-in collection tools in Go 1.28: things like sets, ordered maps, and a cleaner heap for priority queues. In plain English, that means the language is moving closer to offering the kinds of ready-made containers many programmers expected ages ago. But in the comments, the real story isn’t just “nice, useful update” — it’s a full-on why did this take so long? pile-on.
The loudest reaction was a mix of relief and side-eye. One commenter summed up the mood with “better late than never,” while another basically accused Go of slowly reinventing ideas other languages figured out long ago, name-dropping Guy Steele’s famous “Growing a Language” talk. Ouch. Others were happy to see long-missing basics like sets and typed heaps finally arrive, but still used the moment to reopen an old wound: did Go bolt on generics in a clunky way? One commenter said the current system “just isn’t a good fit” and started dreaming aloud about a cleaner Go v2.
And of course, the jokes landed too. There was sarcastic hype for “G2EE” as if this simple library update were some giant enterprise software spec, plus snarky wish-listing about whether database tools might get a modern iterator API “this decade.” Even the supportive crowd had notes, with one person grumbling about mixing in mutation methods. So yes, Go is adding useful new building blocks — but the community has turned the release into a classic tech drama: celebration, nitpicking, old grievances, and memes all at once.
Key Points
- •The Go Collections working group, formed in late 2025, published an umbrella proposal covering several generic collection APIs aimed at Go 1.28.
- •The article says Go’s standard library currently lacks common collection types such as standard sets and ordered maps, despite relying heavily on slices and maps.
- •The proposal builds on generics added in Go 1.18 and iterators added in Go 1.23 to make library-defined collection types more ergonomic.
- •Proposed additions include custom hashing support, hash-based maps and sets, a canonical comparable-element set type, helper functions for legacy sets, an ordered map, and a generic heap API.
- •The article states that initial implementations prioritize simple designs that meet API and asymptotic performance expectations, with further optimizations left for later.