On Oct 18, 2016 12:42 PM, "adonovan via golang-nuts" <
golang-nuts@googlegroups.com> wrote:
>
> On Tuesday, 18 October 2016 15:30:36 UTC-4, Joshua Liebow-Feeser wrote:
>>
>> are there any bits in a pointer which, when modified, won't mess with
the GC?
>
>
> Even if there are, using them would constrain the future choices of the
GC team, for which they will not thank you.
>
> This seems like a bad idea for many reasons.
This is very experimental, so I'm fine doing things that would never
actually be accepted into the runtime. I just want an algorithm that works
with the current gc.
>
> --
> You received this message because you are subscribed to a topic in the
Google Groups "golang-nuts" group.
> To unsubscribe from this topic, visit
https://groups.google.com/d/topic/golang-nuts/3cLrmBoF5B8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
golang-nuts+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
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.
