6 ms·
The story is that the Go designers saw the value in generics and added a bunch of generic container types to the language. They are also saying that if your nee
by vinkelhake 13y ago
The story is that the Go designers saw the value in generics and added a bunch of generic container types to the language. They are also saying that if your needs aren't covered by these built-ins, then you have to build something on your own and you cannot construct something that provides the safety and ease of the built-ins.
> a variety of complex programs are being built and deployed in Golang without generics, which makes it an open question as to whether they're required at all.
And a variety of complex programs have been built and deployed in assembler. There are arguments against adding generics, but the fact that people get by without them isn't a convincing one.
- enneff 13y agoThe story is that generics for Go is an ongoing research project for the team. We are not going to put them into the language until we are sure that we have a satisfactory way of doing it and that the end result is a net win.
- deleted 13y ago[deleted]
- babawere 13y agoIts as been a research project for a very very very long time now ...
- otterley 13y agoIt took Java over 8 years to get generics. Be patient. :)
- coldtea 13y agoYes, because it sure worked well for Java, this slowness...
- enneff 13y agoYeah, we've been busy making the language, libraries, and tools great. Sorry about that.
- jlmendezbonini 13y agoPlease ignore him/her. There are a lot of us who are very excited about the work the Go team is doing.
- coldtea 13y agoSo instead of "research project", a better description would be "very low on the list of priorities, nobody cares about it"?
- enneff 13y agoNo. People continue to work on it. A lot of time has been spent on it. I really don't appreciate your mischaracterization.
- coldtea 13y agoWell, I'm sorry, but I haven't seen this from following Go from a (small) distance -- and doing some work projects with it. Perhaps those people working on it can give an update or some info on their work? Even a "we tried this approach, it's too cumbersome so we abandoned it" or "we pursue this idea, but we're still ways off" etc, would suffice.
- overcyn 13y agoAren't you just kinda being a dick here? A go developer has directly responded to you multiple times, saying that this is a topic that they're actively researching. And you just keep replying with skepticism asking for actual proof. No one owes you anything here. I hope you don't behave this way with other open source projects.
- 13y ago
- coldtea 13y ago>The story is that generics for Go is an ongoing research project for the team. I don't see that in real life. That's just a "shut up" story employed like 4 years ago. If it's an "ongoing research" project, where's any researchy output? "Python 3000" was once a research project and had tons of proposals and research done on various features. Closures in Java were researched, and there were implementations tested. ES6 was an ongoing effort to add features to Javascript, and there have been test implementations, shims, etc before it's out. All languages that wanted to add a feature had attempts by various key developers to add these to them, proposals, papers, testing, requests for comments, etc. Where are those regarding Go and generics?
- enneff 13y agoThe various proposals have been circulated amongst a small group of core Go contributors. That has been sufficient to drive the process so far, with many options being explored in detail. The work continues to evolve. We're not university professors. We're not publishing papers or other "researchy output". We're just trying to get stuff done. If we publish all the works-in-progress we will distract the community from the more pressing concerns of today's Go programmers. We all already spend way too much time reading mail, and generics is a hot topic (obviously). The last thing we need is more (redundant) mail.
- coldtea 13y ago>We're not university professors. We're not publishing papers or other "researchy output". Well neither is Larry Wall, or Guido (well, is not working directly as such), or the Rust guys. But they still manage to put out proposals and describe their approaches to adding features, their progress and such. I didn't mean "researchy output" in the academic sense. Just the results of looking into it, basically. Could be just a blog post. Or some email.
- pstuart 13y agoHow's that Perl 6 coming along? I hear Python 3 is starting to gain traction too.