[go-nuts] Re: Is there a reason go doesn't use the small string optomization

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

Re: [go-nuts] Re: Is there a reason go doesn't use the small string optomization

in it. >> > >> > This proposal was before the fully precise GC we have today. It needs >> to >> > have special GC marking bits for string pointer words (like we did for >> > interface data words so long ago: go1.3ish). I'm not sure we could get &g

[go-nuts] Re: Is there a reason go doesn't use the small string optomization

binary. Am I missing anything else? 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(putting strings on the heap if they will fit within the > sringStruct)to the go runtime, and I realized

Re: [go-nuts] Is there a reason go doesn't use the small string optomization

wrote: > > On Tue, Jan 31, 2017 at 9:10 PM, Eliot Hedeman > > wrote: > > I was writing up a proposal about adding the small string > > optimization(putting strings on the heap if they will fit within the > > sringStruct)to the go runtime, and I realized there might b

[go-nuts] Is there a reason go doesn't use the small string optomization

I was writing up a proposal about adding the small string optimization(putting strings on the heap if they will fit within the sringStruct)to the go runtime, and I realized there might be good reason why this has not been done yet. Are there any glaring reasons you can think of? Here