"Just implement concurrency already" Or maybe "just implement a fast compiler already".
-
-
-
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.
- 4 more replies
New conversation -
-
-
Yeah, cool, a new version of the C preprocessor seems like a totally reasonable solution to this problem.
-
CPP like Disco will never die!
End of conversation
New conversation -
-
-
my favorite implementation of generics in go was the project that used some unicode quotes to mark type parameters and to then to use a template compiler to expand it to different implementations :-/
-
canadian aboriginal syllabic characters 'ᐸ' and 'ᐳ':https://www.reddit.com/r/rust/comments/5penft/parallelizing_enjarify_in_go_and_rust/dcsgk7n/ …
End of conversation
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
We finally have our answer to all those "Who Needs Generics?" articles.
-
We had that ever since they wrote https://golang.org/pkg/sync/#Map which can't be made compatible with builtin maps.
End of conversation
New conversation -
-
-
I can't believe this is happening in 2018.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.