Agreed. But it's not necessarily a "obsolescence" vs "being crushed (...)" thing. With the brainpower behind Go, sure the best things will happen.
I'm not saying that Go has to add generics (or not). In fact generics is just one of the things that I would like to see in Go. There are other things too, that I would like to have in Go; like a faster FFI/CGO, or safe packages by restricting features so that a Go package cannot harm the hosting machine or application, like Safe Tcl <https://en.wikipedia.org/wiki/Tcl>. A list of those things is available here <https://www.quora.com/What-are-the-libraries-tools-you-missed-from-other-programming-languages-in-Golang/answer/Kaveh-Shahbazian?share=c865b9e5&srid=DXs> . On Saturday, February 17, 2018 at 6:10:44 AM UTC+3:30, Dave Cheney wrote: > > I certainly don’t want what happened to C++ to happen to Go. If it’s a > choice between obsolescence or being crushed under the weight of self > inflicted complexity, I’ll gladly vote with my feet for the former. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
