4 ms·
The reason it's not a fair comparison is because go is a barely typed language that requires casting to interface non stop
by deleuze 6y ago
The reason it's not a fair comparison is because go is a barely typed language that requires casting to interface non stop
- 65a 6y agoIf you're casting to interface{} non-stop, you are doing something against the grain of the language. It works, but there's probably a better way of getting the result you are looking for.
- deleuze 6y agoRight, building generic, reusable code is against the grain of the language.
- entha_saava 6y agoI told type system is not the bottleneck, codegen is. Even if you count the size of ode after monomorphization, I am pretty sure the Go compiler compiles it much faster. Because the compiler is not in the benchmarks rat race of adding one optimization pass from every academic paper in the world for diminishing returns. That would be unnecessary for a development compiler. Go compiler could have an optimized slow build option, in ideal world, but that's a different matter altogether.