4 ms·
That's a straw man I believe. Furthermore, other languages seem to have got this right without the fabled runtime/compiler costs that the Go authors seem to ta
by azth 13y ago
That's a straw man I believe.
Furthermore, other languages seem to have got this right without the fabled runtime/compiler costs that the Go authors seem to talk about (see D for instance). What's funny is that there are runtime costs today in Go that could have been resolved by using generics. All interface calls are virtual calls, and cannot be inlined.
> No one disputes that.
Citation needed. I read and heard from many people that do.
- gohrt 13y agoI can't cite my claim that "no one" does something. I'm happy to see any example you provide of the Go team/nuts saying that generics are a bad language idea. Russ Cox, a core Go dev: http://research.swtch.com/generic http://research.swtch.com/generic