From: Derrick Stolee <stolee@gmail.com>
To: Jeff King <peff@peff.net>, amisha <amishhhaaaa@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Elijah Newren <newren@gmail.com>
Subject: Re: [PATCH] sparse-checkout: optimize string_list construction
Date: Sat, 17 Jan 2026 21:39:27 -0500 [thread overview]
Message-ID: <9394755a-18db-4efd-b7c8-ce38eab57f04@gmail.com> (raw)
In-Reply-To: <20260114213551.GC1010080@coredump.intra.peff.net>
On 1/14/26 4:35 PM, Jeff King wrote:
> On Thu, Jan 15, 2026 at 12:58:03AM +0530, amisha wrote:
>
>> Improve O(n^2) complexity to O(n log n) while building a sorted 'string_list' by constructing it unsorted and sorting it afterwards.
...
>> hashmap_for_each_entry(&pl.recursive_hashmap, &iter, pe, ent) {
>> /* pe->pattern starts with "/", skip it */
>> - string_list_insert(&sl, pe->pattern + 1);
>> + string_list_append(&sl, pe->pattern + 1);
>> }
>>
>> string_list_sort(&sl);
>
> Since we already sort here, I was quite curious how this came about. It
> looks like the _insert() call and the _sort() were both added together
> in de11951b03 (sparse-checkout: list directories in cone mode,
> 2019-12-30).
>
> I'd guess it was just a typo/brain-o to mix up append and insert.
This is exactly the case.
> Doesn't the same issue exist in write_cone_to_file(), too (in two
> separate spots)?
It would make sense that such a pattern could reappear in other areas
in this file. I see that you have caught a few more in v3.
Thanks,
-Stolee
next prev parent reply other threads:[~2026-01-18 2:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 19:28 [PATCH] sparse-checkout: optimize string_list construction amisha
2026-01-14 21:35 ` Jeff King
2026-01-18 2:39 ` Derrick Stolee [this message]
2026-01-15 12:56 ` [PATCH v2] " amisha
2026-01-15 13:09 ` [PATCH v3] " amisha
2026-01-15 13:15 ` Amisha Chhajed
2026-01-15 20:09 ` Jeff King
2026-01-16 17:03 ` Amisha Chhajed
2026-01-15 22:26 ` René Scharfe
2026-01-16 8:30 ` Amisha Chhajed
2026-01-16 17:17 ` Junio C Hamano
2026-01-18 2:46 ` Derrick Stolee
2026-01-18 13:09 ` Amisha Chhajed
2026-01-15 13:55 ` Junio C Hamano
2026-01-16 16:50 ` [PATCH] " amisha
2026-01-16 19:11 ` Junio C Hamano
2026-01-18 13:07 ` Amisha Chhajed
2026-01-19 5:32 ` Jeff King
2026-01-19 19:06 ` Junio C Hamano
2026-01-19 12:33 ` [PATCH v5 1/2] " amisha
2026-01-19 17:04 ` Derrick Stolee
2026-01-19 18:33 ` Pushkar Singh
2026-01-20 15:47 ` Amisha Chhajed
2026-01-20 15:38 ` [PATCH v6] sparse-checkout: optimize string_list construction and add tests to verify deduplication amisha
2026-01-20 20:37 ` Derrick Stolee
2026-01-21 13:00 ` [PATCH v7] " Amisha Chhajed
2026-01-21 16:28 ` Derrick Stolee
2026-01-21 16:51 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9394755a-18db-4efd-b7c8-ce38eab57f04@gmail.com \
--to=stolee@gmail.com \
--cc=amishhhaaaa@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox