It's actually really frustrating how folks in the Golang world consistently fight against generics. I get you may not be building data structures. But maybe you'll consume the work of the people who do?
-
-
Replying to @KirinDave
Or you might want to call map(). It’s also weird how many people deny that the Go community is opposed to generics.
1 reply 0 retweets 9 likes -
Replying to @xjones95 @KirinDave
https://github.com/robpike/filter is an argument against generics.
2 replies 0 retweets 0 likes -
Replying to @xjones95 @KirinDave
Rob Pike is arguing that you don’t need filter/map/etc. in a language. The one thing that is holding Go back from being able to express those functions is generics. So Rob Pike is arguing against generics.
0 replies 0 retweets 0 likes
The only reason you would argue against map/filter/etc is to argue against generics. And map/filter/fold are actually pretty interesting when you look at it from an optimization POV. But even more important are parallel versions of those, which demand generics.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.