Just implement generics already. Sheesh. https://github.com/google/gvisor/blob/master/tools/go_generics/generics.go …
-
-
Replying to @pcwalton
"Just implement concurrency already" Or maybe "just implement a fast compiler already".
2 replies 1 retweet 2 likes -
Replying to @sjy
ML-style generics are extremely simple, as I’ve said repeatedly. They’re simpler than Go interfaces. It’s not about implementation difficulty. The problem is that, culturally, the Go team and community don’t want generics. That should change.
3 replies 1 retweet 13 likes -
Replying to @pcwalton
Does "extremely simple" imply monomorphization as an impl strategy? Maybe I'm just tired of horribly slow C++ compilers, but I kinda believe monomorphized generics are not a good default. I'd personally prefer something like Swift's approach (which is complicated).
2 replies 0 retweets 0 likes -
Also, I'm fairly sure "extremely simple" is discounting Go-specific difficulties, e.g. downcasting between interfaces, implicitly implemented interfaces, the difficult question of generic interfaces, and a few others.
1 reply 0 retweets 0 likes -
Replying to @sjy
Downcasting doesn’t interact with generics. The interaction between generic interfaces and structurally typed interfaces seems tricky at first, but I don’t think it actually causes any problems. You just dispatch based on the information the typechecker has at call site.
1 reply 0 retweets 0 likes
I don’t see any problems that Go would have that Java and C# didn’t have.
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.