3 ms·
Would these be people writing "production" code in Go who need generics, and for some reason have not been instead using a language with the features they need?
by bsg75 12y ago
Would these be people writing "production" code in Go who need generics, and for some reason have not been instead using a language with the features they need?
The whole continued argument is odd. The "whole generics are important" and "Go is too simple" thing seems counterintuitive when all of the comments mention Rust, Haskell, Java, etc., yet the proponents of generics are not using those languages instead.
Why if Go does not have the features one needs, would a person be compelled to use it?
- dvirsky 12y agoSimple - it has many other virtues that outweigh this even if you need it. I'm writing a lot of production Go code, and I'm very happy about the language. I wouldn't put generics at the top of my wish list but at times I wish I had them. But not enough that I'm willing to use a 3rd party solution, so I guess not that much :)