> All of those should be generic, but aren't. They aren't because the prevailing... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		xienze on July 13, 2017 \| parent \| context \| favorite \| on: Toward Go 2 > All of those should be generic, but aren't. They aren't because the prevailing attitude is "what do you need generics for? Just do a cast!" The issue is the Go developers are unwilling to consider generics until someone can come up with a problem that absolutely, positively cannot be solved without generics. And of course there isn't one.

bpicolo on July 13, 2017 [–]

I mean, having to cast after every single call to heap is a problem.

Go is turing complete already, so all problems are already able to be solved. :)

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact