I have been arguing passionately against adding generics to Go because I truly believe that it is going against the simplicity of Go and the philosophy behind the design of Go.
I believe that the resilience of Go against unnecessary change is of vital importance. The experience provided by Ken Thompson, Rob Pike and Robert Griesemer in designing Go the way they did speaks for itself. I feel and believe it is of imperative importance to avoid adding things to Go that doesn't present a true and real life day-to-day problem and so far none of the examples the pro-generics camp has provided has been more than minor theoretical examples that do not present any real life problems. I therefore propose that the pro-generics camp provide real examples of problems they have faced that was such a big issue that it justifies adding generics to Go. If all we're presented are these small theoretical examples of sorting lists, etc., then clearly this is nothing but hype that needs to go away. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/19560461608790506%40sas1-75175cadc2b3.qloud-c.yandex.net.
