I honestly think that if Go let you abstract over its built-in containers (e.g. a 'Slice' typeclass) and integers (e.g. a 'Num' typeclass) it would solve 90% of the problems that cause people to push for full-blown generics.
Show this thread
You don't really want generics. You want to write map/filter/reduce/sort/reverse instead of yet another for loop, you want to have heaps and linked lists without interface{}, and you want min/max functions. I could only find one Experience Report that suggested otherwise.
-
-
Fully agree! I am in the no-generics camp, and believe this would be a fantastic middle ground. Unsure of how it's implemented though.. similar to make/append/other "generic" builtins I suppose.
-
Check out my compile-to-Go language that does basically this:https://github.com/lukechampine/ply …
- 1 more reply
New conversation -
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.