3 ms·
The Go team's stance on generics, summarized: For us to consider generics, show us an implementation, that: 1. Doesn't hurt compile times too much. 2. Doesn't
by PopsiclePete 8y ago
The Go team's stance on generics, summarized:
For us to consider generics, show us an implementation, that:
1. Doesn't hurt compile times too much.
2. Doesn't bloat the binary too much.
3. Doesn't hurt run-time performance too much.
4. Doesn't fundamentally change the language syntax too much.
5. Doesn't complicate the type system too much.
6. (My personal fav) - Plays nicely with Go interfaces. (Seriously, good luck with that one!)
Show us that and no problem - you'll get generics!
Now before you go off and waste months doing that, realize that it's them basically politely telling the community to piss off with these generics proposals. But they're free to write comments in a dozen or so Github issues if it makes them feel better, why not.
If you've been following the language since 2010 or so, like I have, you'd know by now that roughly 4 well-thought generics proposals have been shot down by the core team.
Programmers are really horrible with emotional intelligence and reading between the lines, it seems.