git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Project idea: strbuf allocation modes

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 19, 2014, 00:55 UTC
Message-ID
<xmqq38hab0js.fsf@gitster.dls.corp.google.com>
In-Reply-To
<5351854E.1080602@alum.mit.edu>
Michael Haggerty <mhagger@alum.mit.edu> writes:
Show 20 quoted lines
> On 04/18/2014 07:21 PM, Junio C Hamano wrote:
>> Michael Haggerty <mhagger@alum.mit.edu> writes:
>> 
>>> The Idea
>>> ========
>>>
>>> I would like to see strbuf enhanced to allow it to use memory that it
>>> doesn't own (for example, stack-allocated memory), while (optionally)
>>> allowing it to switch over to using allocated memory if the string grows
>>> past the size of the pre-allocated buffer.
>> 
>> I'd like to see these characteristics, but I would want to see that
>> this is done entirely internally inside the strbuf implementation
>> without any API impact, other than the initialisation.  I do not
>> ...
>
> I think that's exactly what I described.  The only thing that would have
> to change in the strbuf behavior (aside from initialization) is that a
> buffer-growing operation might die if the string would grow outside of
> the bounds of the existing buffer when STRBUF_FIXED_MEMORY is set.
Yup, we are in agreement ;-)

More seriously, sorry for sounding as if I was objecting. I should have edited s/but/and/ before sending my response out.

Thanks.
Previous: Michael HaggertyNext: Matthieu Moy
Message 5 of 8 in “Students project on Git (Ensimag)”
  1. Matthieu MoyApr 8, 2014
  2. Project idea: strbuf allocation modesMichael Haggerty, Apr 18, 2014
  3. Junio C HamanoApr 18, 2014
  4. Michael HaggertyApr 18, 2014
  5. Junio C HamanoApr 19, 2014
  6. Matthieu MoyApr 22, 2014
  7. Michael HaggertyApr 22, 2014
  8. Matthieu MoyApr 22, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.