4 ms·
> I'm pretty sure the feature will show up in the next few minor version increments. No it won't. People need to stop expecting generics because it will never
by aikah 11y ago
> I'm pretty sure the feature will show up in the next few minor version increments.
No it won't. People need to stop expecting generics because it will never happen. Not that agree with this but it was made pretty clear in the go-nuts mailing list that the Go team wants to keep Go type system "simple".
- nsajko 11y agoMaybe in Go 2? ;)
- MikeTaylor 11y agoNever gonna happen, Go 2 is considered harmful.
- api 11y agoThis is one of the things I like about Go: it's "done." In exchange for passing on extensions that might make certain use cases easier, we'll avoid the bloat and have decades of backward compatibility. We just came out of a decade of nifty language mania. What I learned is that languages are boring but problems are interesting. Algorithms and solutions are interesting. A great solution to a challenging problem is really interesting even if it's in the most boring language ever. I have code on my machine written in C in the 70s because C is largely "done." People today continue to write interesting stuff in C. Neuromancer was written in the same language as Lord of the Rings and Moby Dick, too.
- yokohummer7 11y agoC is clearly not done, actually. Both C99 and C11 added, deprecated, and even removed many features. You can run C in the 70s not because it didn't change, but because it retained backward compatibility. It will be pretty surprising if Go manages to prohibit even the same level of changes C has taken.
- zeckalpha 11y agoWhat C compiler do you use to compile that 70s code? I find modern compilers usually choke on the "done" C code from then.
- jschwartzi 11y agoYou have to feed it a switch or two, but gcc will do it. Of course, we're talking about pre-ANSI C where any function prototype without a void argument implicitly accepts any and all arguments.
- zeckalpha 11y agoANSI was 9 years after the 70s. I'm curious about the 70s C code that was "done". My point is that Go may still be in the 70s.
- JonahBraun 11y agoYou missed the joke re: Go 2. I don't think Go is done. The active development speaks otherwise.
- MikeTaylor 11y agoI think everyone missed it. Glad you, at least, didn't :-)