News for hackers. Stuff that matters.

A comment on Go Execution Modes. Parent comment

Re:Go Execution Modes by crawshaw on Thursday September 04, 2014 @12:19PM (#8269108)
The GC will not update a pointer once it is converted to the type uintptr. It becomes invisible to the precise collector, so the uintptr acts as an id value.
[ Parent | on HN ]
Re:Go Execution Modes by pjmlp on Thursday September 04, 2014 @12:52PM (#8269314)
Worse, it might be collected then as the collector might think it is no longer in use.
[ Parent | on HN ]
Re:Go Execution Modes by ianlancetaylor on Thursday September 04, 2014 @02:36PM (#8269886)
But it's in the map, so it's in use.
[ Parent | on HN ]
Re:Go Execution Modes by pjmlp on Thursday September 04, 2014 @02:44PM (#8269936)
This remark is what triggered my comment

> It becomes invisible to the precise collector

So does the conversion to uintptr remove it from the root lists the GC searches?

[ Parent | on HN ]
Re:Go Execution Modes by crawshaw on Thursday September 04, 2014 @03:01PM (#8270022)
It's a map[uintptr]unsafe.Pointer. The key is invisible to the collector, but the value is an unsafe.Pointer, which is will be managed for you by the precise collector.
[ Parent | on HN ]
Re:Go Execution Modes by pjmlp on Thursday September 04, 2014 @04:57PM (#8270595)
Ah, stupid me! Thanks for clarifying it.
[ Parent | on HN ]