It is already broken ;)<p>In c++ indexing vector does no range checks while in Go indexing slice checks validity of index.<p>And vector in gcc growths by factor of 2 while slice in Go grows by 25% after it&#x27;s bigger than 1024 elements. So there is a trade-of between memory usage and number of allocations.<p>And... I could go on, but the point is that microbenchmarks are in general not that useful :)