3 ms·
Ignoring the inappropriate ad hominem... Why not type the loop variable as int64 in go? Why not just use an int, which would default to int64 on a 64 bit syste
by jamra 11y ago
Ignoring the inappropriate ad hominem...
Why not type the loop variable as int64 in go? Why not just use an int, which would default to int64 on a 64 bit system? Why not just use sum := 0?
Generally benchmarks don't say much unless one of the languages perform extremely poorly. This benchmark doesn't say anything of value.
- masklinn 11y ago> Ignoring the inappropriate ad hominem... Seems appropriate to me, you're trying to spin a shit "benchmark" into some sort of conspiracy theory against your pet language and for your arch-nemesis or something. > Why not type the loop variable as int64 in go? Have you actually read my comment? 1. why not indeed, maybe because it's kind of a pain in the ass to do? 2. and that's got no relevance anyway, it changes pretty much nothing to the runtime > Why not just use an int, which would default to int64 on a 64 bit system? Because leaving that stuff to random half-specified defaults is a terrible idea when you have exact-sized integers you can be certain of. > Why not just use sum := 0? Because if integral numbers don't default to 64 bits or more or arbitrary-size integers, you get signed overflows.