4 ms·
>Besides, has anyone seen much experiments, with actual coding or at least design, for finding this "non-complicated" way anyway? Proposal from Ian Lance Taylo
by gribbly 10y ago
>Besides, has anyone seen much experiments, with actual coding or at least design, for finding this "non-complicated" way anyway?
Proposal from Ian Lance Taylor, Go developer at Google
https://github.com/golang/proposal/blob/master/design/15292-generics.md https://github.com/golang/proposal/blob/master/design/15292-...
View of Russ Cox, Go developer at Google
https://research.swtch.com/go2017#generics https://research.swtch.com/go2017#generics
- coldtea 10y agoYeah, I've read both -- and more. None of this is what I described: either actual code, even if in some experimental compiler branch/fork, or at least a concrete design. Ian's just reiterates the various options (Rob Pike has already written similar things), and Russ Cox is just several vague ideas for future additions to the language.
- deleted 10y ago[deleted]
- crypto5 10y agoSo, Russ says it is Ok to have generics but there are higher priorities. The problem with this approach is that eventually when they will add generics, there will be whole ecosystem living without them, which means this ecosystem will need to be entirely reimplemented.
- gribbly 10y agoWhy ? It's not as if the old code needs to be rewitten just because there is the option of generics.