Thank you so much for pointing this out. I didn't realize that map
won't shrink in go, that's pretty counter intuitive.
I also found the issue here:
https://github.com/golang/go/issues/20135
It looks like the right direction.
On Sun, Oct 9, 2022 at 2:29 PM wagner riffel wrote:
>
> On 08/10/2022
On 08/10/2022 22:56, davy zhang wrote:
Original post on stackoverflow:
https://stackoverflow.com/questions/73985794/for-range-loop-variable-passing-by-reference-to-go-routine-causes-memory-leak
Code for reproducing the problem:
https://go.dev/play/p/7Xzx1Aauzhh
go version go1.19 darwin/amd64
Hi all, I have a few question regarding Go compiler optimizations.
How Go Compiler (gc) optimize methods with value or pointer receiver (or
functions)?
Does a method with value receiver always create a copy of data to its stack
or the copy happend if there's a write attempt to it (CoW, or used f
For anyone who might be interested;
https://googlegroups2rss.ferdypruis.dev/rss/golang-announce.xml.rss
I generate this feed myself by scraping the group.
On Thursday, July 29, 2021 at 9:01:19 PM UTC+2 Sebastien Binet wrote:
>
> Jul 28, 2021 18:02:06 Ferdy :
>
> > Up until this morning I had
