[mseepgood]

Not having generics was never a fixed decision. The FAQ said since day one that they "may well be added at some point" and that "The topic remains open", so there was no "walking back".

By the way, not having ADTs is not a fixed decision either.

You seem to mistake the fact that the Go team is in no rush to add things to the language as a general rejection of these things.

[Mawr]

It doesn't matter. What does is Go 1.0 shipped without generics. That single decision immutably affected the entire language. Now that generics have been retrofitted, the issues are clear as day:

- Awkward transition period between a stdlib with and without generics: [1]

- Completely different APIs for built-in data structures (slices, maps) and generic ones

- Lack of obvious follow-up features that would have been there at 1.0 if generics were added, e.g. iterators

[1]: https://github.com/golang/go/discussions/48287