4 ms·
> Honestly I keep seeing this in all big go project, despite the lack of generics. Not maybe because of the lack of generics?
by r-u-serious 7y ago
> Honestly I keep seeing this in all big go project, despite the lack of generics.
Not maybe because of the lack of generics?
- siscia 7y agoI am not sure myself. If I recall correctly one of the arguments for lack of generic was that they would make more obvious code, hence easier to follow and read. Actually it seems like the lack of generic just make more obvious code, hence more difficult to read. The other argument was compilation speed, that honestly I cannot complain about.
- jeremyjh 7y ago> If I recall correctly one of the arguments for lack of generic was that they would make more obvious code I don't believe that is a reason ever articulated by the core team, but a post-hoc justification by apologists. The reason the core team gave was that they had not settled on a design that would fit well with their other goals for the language, and it simply didn't make the short list for 1.0.