It's not that "they" aren't listening. There's a limited number of developers working on the language, there are many other problems being solved.
So far despite all the people lamenting the lack of generics in Go I've yet to have seen someone propose a viable (eg: backwards compatible, realistic to achieve with the current compilers and runtime, etc.) way to implement, nevermind someone who's produced a prototype.
Maybe that sort of thing will be easier once more of the toolchain is rewritten in Go later this year.
I don't think anyone is denying that generics make writing certain types of code easier, but it's worth getting them right since major language additions are something you need to support for a long time.
So far despite all the people lamenting the lack of generics in Go I've yet
to have seen someone propose a viable (eg: backwards compatible, realistic
to achieve with the current compilers and runtime, etc.) way to implement,
nevermind someone who's produced a prototype.
This seems to make it even more of an issue that they weren't included in the first place. Based on your statement, it's likely that when generics are finally added, they will initially cause the community some pain or they will feel tacked on.
> So far despite all the people lamenting the lack of generics in Go I've yet to have seen someone propose a viable (eg: backwards compatible, realistic to achieve with the current compilers and runtime, etc.) way to implement, nevermind someone who's produced a prototype.
It's kind of crazy to prioritize anything other than generics and exceptions. If Go never catches on, those will surely be why, and IMHO rightly so, it's just unreasonably hard to write correct code without them.
So far despite all the people lamenting the lack of generics in Go I've yet to have seen someone propose a viable (eg: backwards compatible, realistic to achieve with the current compilers and runtime, etc.) way to implement, nevermind someone who's produced a prototype.
Maybe that sort of thing will be easier once more of the toolchain is rewritten in Go later this year.
I don't think anyone is denying that generics make writing certain types of code easier, but it's worth getting them right since major language additions are something you need to support for a long time.