This caught my eye because I recall you being someone who has vigorously criticized Go in every single Go discussion. A quick search and I can find lengthy critiques from you going back four years.
It very much seems like you haven't moved on.
This caught my eye because I recall you being someone who has vigorously criticized Go in every single Go discussion. A quick search and I can find lengthy critiques from you going back four years.
It very much seems like you haven't moved on.
If you read correctly my post, I just said I would like to see the discussion about generics take into account what other generic systems besides Java and C++ offer.
In those four years as you say, I have never seen such a document, even most discussions on gonuts went around Java, C++ and .NET implementations.
There are mentions that a prototype was made, yet the conclusions haven't been shared with the outside world.
If the designers don't want to implement generics, I can always look to Go as Active Oberon with C like syntax.
I see more value arguing about using Go for user space applications that are still made in C, just because the authors needed a compiled language than arguing about the essence of generics in Go. That boat has long left.
Edit: Just got to read Ian's opinion, quite interesting.
https://groups.google.com/forum/#!msg/golang-dev/Zx2uSqvMS0Q...