Go 2 Draft Designs

Re:Go 2 Draft Designs by krylon on Tuesday August 28, 2018 @02:33PM (#17861507)

I basically agree. I still think, while we're at it, making Generics a general feature of the language would probably be easier than adding all kinds of special cases.

But yeah, if Go just added a generic map/filter mechanism (Python's list comprehensions (in turn inherited from Haskell) look very nice), that would cover about %75 of the use cases I want Generics for. Add a generic mechanism to use the range operator with user-defined types, and we're at about 95%.

[ Parent | on HN ]

Re:Go 2 Draft Designs by thiht on Wednesday August 29, 2018 @08:23AM (#17867647)

> Python's list comprehensions (in turn inherited from Haskell) look very nice

Do they? I find them hard to read and hard to chain. I tend to prefer basic map, filter, reduce methods

[ Parent | on HN ]

Re:Go 2 Draft Designs by krylon on Friday August 31, 2018 @05:48PM (#17888800)

Mmmh, that is a good point. I never used nested list comprehensions, to be honest, and I have not used Python in a couple of years. For non-nested cases, they are very nice, though.

OTOH, I never used nested map/remove-if constructs in Lisp, because that, too, can get rather annoying to read.

[ Parent | on HN ]