3 ms·

Not that I even care that much, but that's total crap. Compile-time generics, which is what most people seem to be referring to when they say they want generics

by hacknat 11y ago

Not that I even care that much, but that's total crap. Compile-time generics, which is what most people seem to be referring to when they say they want generics in Go, are eminently doable. It would not be hard to implement. Runtime generics are probably possible as well. What are you even basing your assertion on? Edit: What do you mean, "there will never be a 2.0"? Do you have a crystal ball?

pjmlp 11y ago
The team has already stated "The language design is done".
- grey-area 11y ago
  The issues list has a bunch of breaking changes they've put off to Go2. It won't come soon, but probably at some point they will produce a Go2, if only to fix a few small annoyances and things they got wrong in the stdlib which would otherwise break the Go1 pledge. Of course, that doesn't mean Go2 will introduce lots of huge changes to the language, I doubt very much it would, but it probably will happen sometime. https://github.com/golang/go/issues?q=is%3Aopen+is%3Aissue+label%3AGo2 https://github.com/golang/go/issues?q=is%3Aopen+is%3Aissue+l... As another datapoint, here are the answers of the team to a question on what they dislike about Go1. These are mostly breaking changes which would require a Go2. I don't think anyone is hostile to it long-term, they're just not in a hurry. There is a huge value to developers in not having churn in an ecosystem and breaking changes, I and many others really value that and am pleased they take this approach. https://www.reddit.com/r/golang/comments/46bd5h/ama_we_are_the_go_contributors_ask_us_anything/d03s41s https://www.reddit.com/r/golang/comments/46bd5h/ama_we_are_t... So I think you've misinterpreted the above statement, it was probably an off hand remark in response to proposals for Go1 which would have radically altered the language (I can find no ref to it on the web, 0 results for that phrase).
  - pjmlp 11y ago
    Update to my reply. "So… when is Go 2?", Slide 38 "No plans. Maybe never.", Slide 39 https://docs.google.com/presentation/d/1JsCKdK_AvDdn8EkummMNvpo7ntqteWQfynq9hFTCkhQ/view?slide=id.p&pref=2&pli=1#slide=id.g118cf9b85c_0_404 https://docs.google.com/presentation/d/1JsCKdK_AvDdn8EkummMN...
  - pjmlp 11y ago
    It was done at one Strange Loop talk if I recall correctly.
aikah 11y ago
> Compile-time generics I don't even know if it's possible at this point, since it would break Go's reflection library. No IMHO it's designed not to be extendable at all.

by hacknat 11y ago

pjmlp 11y ago

The team has already stated "The language design is done".

grey-area 11y ago
The issues list has a bunch of breaking changes they've put off to Go2. It won't come soon, but probably at some point they will produce a Go2, if only to fix a few small annoyances and things they got wrong in the stdlib which would otherwise break the Go1 pledge. Of course, that doesn't mean Go2 will introduce lots of huge changes to the language, I doubt very much it would, but it probably will happen sometime. https://github.com/golang/go/issues?q=is%3Aopen+is%3Aissue+label%3AGo2 https://github.com/golang/go/issues?q=is%3Aopen+is%3Aissue+l... As another datapoint, here are the answers of the team to a question on what they dislike about Go1. These are mostly breaking changes which would require a Go2. I don't think anyone is hostile to it long-term, they're just not in a hurry. There is a huge value to developers in not having churn in an ecosystem and breaking changes, I and many others really value that and am pleased they take this approach. https://www.reddit.com/r/golang/comments/46bd5h/ama_we_are_the_go_contributors_ask_us_anything/d03s41s https://www.reddit.com/r/golang/comments/46bd5h/ama_we_are_t... So I think you've misinterpreted the above statement, it was probably an off hand remark in response to proposals for Go1 which would have radically altered the language (I can find no ref to it on the web, 0 results for that phrase).
- pjmlp 11y ago
  Update to my reply. "So… when is Go 2?", Slide 38 "No plans. Maybe never.", Slide 39 https://docs.google.com/presentation/d/1JsCKdK_AvDdn8EkummMNvpo7ntqteWQfynq9hFTCkhQ/view?slide=id.p&pref=2&pli=1#slide=id.g118cf9b85c_0_404 https://docs.google.com/presentation/d/1JsCKdK_AvDdn8EkummMN...
- pjmlp 11y ago
  It was done at one Strange Loop talk if I recall correctly.

aikah 11y ago

> Compile-time generics I don't even know if it's possible at this point, since it would break Go's reflection library. No IMHO it's designed not to be extendable at all.