Re: [GSoC][RFC][PATCH 2/2] STRBUF_INIT_CONST: Adapting strbuf_* functions
- From
Robear Selwans <rwagih.rw@gmail.com>
- Date
- Feb 19, 2020, 04:34 UTC
- Message-ID
- <CALH1-XoXdpAxYj7r1ouc-v4KrVuYDocBFFC++7eFiRwdHFxmUA@mail.gmail.com>
- In-Reply-To
- <xmqqv9o3gthb.fsf@gitster-ct.c.googlers.com>
On Wed, Feb 19, 2020 at 5:13 AM Junio C Hamano <gitster@pobox.com> wrote:
Show 16 quoted lines
>
> Yes, but the case that matters to _your_ use is sb->alloc == 0. You
> do not want to let a broken strbuf (presumably broken by changes
> other than your own) to pass, when you can detect it. And for that,
> paying attention to sb->len _might_ make sense, but then the check
> won't be
>
> if (sb->alloc < sb->len)
> make it mutable;
>
> you'd rather be writing something like
>
> if (!sb->alloc)
> make it mutable;
> else if (sb->alloc < sb->len)
> BUG("somebody fed a corrupt strbuf to me");Ooh so what you meant, is that corrupt `strbuf`s need to be anticipated even if they don't make much sense. Smart.