4 ms·
Wasn’t performance the argument against generics in GO? Were they just obstinate?
by AtNightWeCode 4y ago
Wasn’t performance the argument against generics in GO? Were they just obstinate?
- oconnor663 4y agoI think complexity was the main argument against, and the majority opinion around performance was that the status quo was good enough. Unless you meant compile-time performance, in which case yes that was another argument against.
- AtNightWeCode 4y agoThank you. Now I remember. It was compile-time performance not the actual performance.
- deleted 4y ago[deleted]
- topspin 4y agoA key driver of Go design was compiler performance. Generics make the compiler more complex, use more memory, etc. and presumably require a less performant compiler. I don't know what the implications are for Go with generic types. Either they've convinced themselves that a fast generic capable compiler is possible or the the compiler performance goal is no longer the high priority it once was.