I find it interesting that they're asking the community what the use cases for generics are, when internally Go does support generics for its built-in collectio

I find it interesting that they're asking the community what the use cases for generics are, when internally Go does support generics for its built-in collection types...hmmm I wonder why?! Maybe because it provides compile-time type safety and reduces the amount of boilerplate that would otherwise be required. Yet they can't see the usefulness outside of this single case? Seems disingenuous to me.