The way the post you're responding to was phrased is indeed hyperbolic. But I think there is a valid point that compiler performance concerns are a pretty unconvincing reason to not have generics, especially in light of a demonstrated high tolerance for compiler performance regressions.
Re:Golang on ARM
by tedunangst on Tuesday November 17, 2015 @08:02PM
(#10585209)
Why not consult the go faq to find their reasoning for omitting generics?
> Generics are convenient but they come at a cost in complexity in the type system and run-time. We haven't yet found a design that gives value proportionate to the complexity, although we continue to think about it.
The word performance doesn't appear in that paragraph.
[deleted]
[deleted]
You're right, that was really stupid of me. I'll delete it.
Re:Golang on ARM
by AnimalMuppet on Tuesday November 17, 2015 @08:21PM
(#10585282)
Complexity in the type system can easily have a negative effect on compiler performance.
Absolutely nobody in the universe promised you generics in Go. You may never, ever get them; the longer the language thrives without them, the less urgent they seem.