3 ms·
> Go has generic container types, so woot, no need for plain generics. There are dozens of common types that give the lie to this (the standard Go claim), like
by morelisp 7y ago
> Go has generic container types, so woot, no need for plain generics.
There are dozens of common types that give the lie to this (the standard Go claim), like sync.Map, sync.Value, lru, or pool.
Type classes are a feature that arises from having generics, not one that you need to take advantage of generics.