What version of Go are you using (go version)?

$ go version
go version go1.15.6 linux/amd64

Does this issue reproduce with the latest release?

Not related

What operating system and processor architecture are you using (go env)?

i5/ubuntu

What did you do?

In the golang blog of pprof, they demonstrate the performance of golang via a benchmarking code and then comparing with cpp counterpart. The blog tells about reallocartion of memory and its time complexities in multiple loops.

The blog => https://blog.golang.org/pprof

So, I builded the examples mentioned in the havlak repository.
But to find out, that the variable "size" is static throught the execution, to be precise, 252013.

What did you expect to see?

The constant value of size parameter, doesn't triggers the the memory re-allocation, measuring whose cost is the most focused part of the blog.

What did you see instead?

As the blog uses the havlok example as a memory critical task, It isn't actually.