> having int be variable-sized allows you to easily have maps or other int-indexed structures that naturally grow in capacity with the current architecture ... Go programming that targets 32-bit ARM CPUs and the…
> (int mirrors the native bit-ness of the architecture in Go instead of virtually always being 32-bit like it is in C/C++). Seriously, in a language designed ~2010 a common "int" variable could be 32-bit? 64-bit…
> when he really should have blamed the Dunning-Kruger effect. Going a layer deeper, blame the competitions themselves. They very rarely have good data sets to actually weed out algorithmically poor solutions, so…
> having int be variable-sized allows you to easily have maps or other int-indexed structures that naturally grow in capacity with the current architecture ... Go programming that targets 32-bit ARM CPUs and the…
> (int mirrors the native bit-ness of the architecture in Go instead of virtually always being 32-bit like it is in C/C++). Seriously, in a language designed ~2010 a common "int" variable could be 32-bit? 64-bit…
> when he really should have blamed the Dunning-Kruger effect. Going a layer deeper, blame the competitions themselves. They very rarely have good data sets to actually weed out algorithmically poor solutions, so…