> It is a solved problem. This is debatable. Is it a problem that's solved well? Is it solved in the best way possible and there could never be a better way to

> It is a solved problem. This is debatable. Is it a problem that's solved well? Is it solved in the best way possible and there could never be a better way to do generics? I think not. I think it's solved adequately, but not great. Compared to the other facilities that Go offers, generics are typically pretty messy and add significant complexity to the language, tools, parsing, reasoning, compilation times, etc. > It's just not there because of.. What? Stubbornness? I'm not sure. But then it irritates me to copy paste stuff. This statement is ill-informed. Have you seen https://github.com/golang/go/issues/15292 https://github.com/golang/go/issues/15292 and https://github.com/golang/proposal/blob/master/design/15292-generics.md https://github.com/golang/proposal/blob/master/design/15292-...? Have you considered all the ways in which it will affect the language and the trade-offs? Once generics are added to Go, they will forever be there, together with all the disadvantages and missed opportunities, and we'll have to live with them. That's not a thing to be taken lightly. In comparison, maybe copying a little here and there isn't all that bad.