I am moving this discussion to this proposal. Thanks for the pointers(pun
intended) https://github.com/golang/go/issues/18894#issuecomment-276900485
On Tuesday, January 31, 2017 at 9:12:24 PM UTC-8, Eliot Hedeman wrote:
>
> I was writing up a proposal about adding the small string
> optimization
Thanks for the info! I will for sure take a look before submitting my
proposal
On Wednesday, February 1, 2017 at 5:34:53 PM UTC-8, Keith Randall wrote:
>
> &$*@^! Google! Apparently "publish to the web" doesn't mean publish to
> the web when you're inside Google.
>
> But I can publish to a pdf
This discussion reminds me of another technique I've seen, which is to use
tagged pointers to store strings of max length 7 with no allocations at all.
Apologies if this has already been discussed to death here.
For background: tagged pointers take advantage of the fact that most
architectures
&$*@^! Google! Apparently "publish to the web" doesn't mean publish to the
web when you're inside Google.
But I can publish to a pdf and then attach it...
On Wed, Feb 1, 2017 at 5:24 PM, Caleb Spare wrote:
> Your document is not accessible to me. (Google-internal?)
>
> On Wed, Feb 1, 2017 at 5
Your document is not accessible to me. (Google-internal?)
On Wed, Feb 1, 2017 at 5:18 PM, 'Keith Randall' via golang-nuts
wrote:
> I wrote up a proto-proposal for something like this a while ago.
>
> https://docs.google.com/a/google.com/document/d/18nu6QTr-ACYr5AiyP6x31SkXvuJZZaZ12lnvPTEQfgQ/pub
I wrote up a proto-proposal for something like this a while ago.
https://docs.google.com/a/google.com/document/d/18nu6QTr-ACYr5AiyP6x31SkXvuJZZaZ12lnvPTEQfgQ/pub
It has a few numbers worth looking at in it.
This proposal was before the fully precise GC we have today. It needs to
have special G
On Wed, Feb 1, 2017 at 10:38 AM, Eliot Hedeman
wrote:
> Ok, I'm going to try to restate the issues raised and answer them one by
> one. If I misunderstand, please let me know.
>
> 1. The GC needs to know if a pointer is actually a pointer.
> Solution: Check if the high bit is set. If it is, you kn
Ok, I'm going to try to restate the issues raised and answer them one by
one. If I misunderstand, please let me know.
1. The GC needs to know if a pointer is actually a pointer.
Solution: Check if the high bit is set. If it is, you know for sure that it
is not a pointer.
It actually doesn't matt
