back. We can fix the pointer scan problem by moving overflow back to the
bucket header, and then we can fix the pointer walking problem that the
overflow move fixed by adding a dummy word to the header. I don't want to
have to look at code like in CL 85e7bee and wonder whether it's correct.
It's not obviously incorrect but it's not obviously correct either. Why
bother with the complexity?
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/d/optout.