On Wed, Aug 22, 2018 at 8:20 AM, 'Florian Uekermann' via golang-nuts
<golang-nuts@googlegroups.com> wrote:
> On Tuesday, August 21, 2018 at 7:31:28 AM UTC+2, Keith Randall wrote:
>>
>> There is no conservativeness to unsafe.Pointer. The type information for
>> any object in the heap is recorded at allocation time, and is unrelated to
>> the type of the reference currently held to it (be it unsafe.Pointer,
>> []byte, *int64, or whatever).
>> So for 2.2, the answer is no, you are incorrect.
>
>
>>
>> On Monday, August 20, 2018 at 4:56:00 PM UTC-7, Kevin Malachowski wrote:
>>>
>>> That information is old now - Go has a precise GC now. There is some sort
>>> of metadata stored for each variable related to whether the type contains
>>> pointers (as Jan alluded to earlier in the thread).
>
>
> Thanks guys! That is very good to know. How recent is this change? (what is
> the minimum compiler version I need for this?)

Go 1.5, I think.

Ian

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to