News for hackers. Stuff that matters.
Re:Go 2016 Survey Results by grey-area on Monday March 06, 2017 @10:27AM (#13803254)
I have some sympathy here - generics is hard to get right, and language changes are forever. As a Go user, I have absolutely no problem with them taking their time on this and only introducing it (probably with Go 2) when it has been thoroughly thought through. There are workarounds (writing for specific types, go generate).
Re:Go 2016 Survey Results by MichaelGG on Monday March 06, 2017 @10:36AM (#13803315)
Generics have been around for decades. It seems very unlikely that Go will discover some entirely new way to implement them. They'll end up implementing them the same way they would have if they'd done it years ago. The tradeoffs are well known.
Re:Go 2016 Survey Results by coldtea on Monday March 06, 2017 @10:36AM (#13803317)
>I have some sympathy here - generics is hard to get right

What does "right" mean? All kinds of languages, even pet projects, managed to implement them just fine.

Except if we mean "perfect, in a way that avoids all engineering tradeoffs".

But why would Generics especially need to be perfect in a language full of other engineering tradeoffs?