4 ms·
It seems plausible that some people who might otherwise want to have decided not to given the very vocal contingent of the Go community that's been opposed to g
by saghm 5y ago
It seems plausible that some people who might otherwise want to have decided not to given the very vocal contingent of the Go community that's been opposed to generics. After almost a decade of people saying Go didn't need generics, it seems like it would be hard to convince people who are knowledgeable in that field that their efforts would be welcome.
- randomdata 5y agoThe core Go team has been working on generics since the pre-1.0 days and have submitted many different generics proposals over the years to reflect that. They all, until the latest one, failed for one reason or another, but shared property of them all was being created by those who were not experts in the domain. It is why the latest incarnation brought in an external consultant to help guide the team in the right direction. There was clearly always interest from the project itself. There may have been some random naysayers on the internet who act like they are opposed, but you'll find people acting every way imaginable on the internet. I really doubt anyone actually refrained from working on the project because an internet troll wrote something silly.
- andrekandre 5y agowhat is the major difference of go generics vs say c# or swift generics that makes the long wait worth it for go? was there any major breakthroughs?
- randomdata 5y agoI don't expect you will find any major difference, hence why the number of people who cared about generics in Go was effectively nobody and why very few were stepping up to contribute: They already had many other languages to choose from.
- xh-dude 5y agoIt seems significant (major? I dunno) that Go doesn’t have inheritance or subclassing or co-/contra-variance.