Re:Proposal: Go 2 transition
by int_19h on Friday October 26, 2018 @07:21PM
(#18313395)
I think it's more that it requires it in many cases, due to the lack of generics.
[ Parent
| on HN ]
Re:Proposal: Go 2 transition
by the_clarence on Saturday October 27, 2018 @12:33AM
(#18314370)
I always find work arounds or just write more code. I feel like it's annoying sometimee but when reading code I feel blessed that generics are not supported.
Re:Proposal: Go 2 transition
by erik_seaberg on Saturday October 27, 2018 @07:10PM
(#18318215)
Reading redundant code is always more work than letting the computer handle those low-payoff details.
And nobody's going to provide their data structures specialized to every type you could possibly want. Case in point: container/heap from the standard library takes and returns interface{}.
Re:Proposal: Go 2 transition
by the_clarence on Saturday October 27, 2018 @07:56PM
(#18318357)
Oh no. Believe me reading code full of templates is not a pleasure. There is a reason Go is so pleasant to read.
C++ templates are hardly the best example of generics out there, and certainly not what you should be looking at from a Go perspective, seeing how Go is a higher-level language that doesn't concern itself with zero-cost abstractions anywhere near as much as C++ does. Look at C# or D generics instead.