News for hackers. Stuff that matters.
Re:Generics aren't ready for Go by weberc2 on Monday February 18, 2019 @06:32PM (#19195470)
On a phone, so sorry in advance for terse response. Agreed that the language would be simpler in some sense with generics; I don’t think it would be more readable due to aforementioned increase in expressivity. Interesting point about first class functions, and while I largely agree, the variation in Go code is still small and constrained which is my point. :)
Re:Generics aren't ready for Go by yawaramin on Monday February 18, 2019 @07:43PM (#19195811)
You don't find the existing Go code using the built-in generics (arrays, dictionaries, channels) readable? You find that its expressiveness makes it too complex?
Re:Generics aren't ready for Go by weberc2 on Tuesday February 19, 2019 @08:46AM (#19198873)
Sorry if I haven’t articulated my position very well: the property I care about is consistency of code throughout the ecosystem which exist due to the constraints such as the absense of user-defined generics. Hopefully that’s a little clearer, and makes it obvious why “a few built in genetics” is fundamentally different than user-defines generics.