From: "René Scharfe" <l.s.r@web.de>
To: Amisha Chhajed <amishhhaaaa@gmail.com>, git@vger.kernel.org
Cc: gitster@pobox.com, stolee@gmail.com, newren@gmail.com, peff@peff.net
Subject: Re: [PATCH v3] sparse-checkout: optimize string_list construction
Date: Thu, 15 Jan 2026 23:26:49 +0100 [thread overview]
Message-ID: <fc14e0e5-93bc-4805-a20d-d2aa4eb87ddb@web.de> (raw)
In-Reply-To: <CAPvEtreX9sGHUn7+Y0kLo_VnK7Y=OYLq-kz-+np3bu1QtoEpnA@mail.gmail.com>
On 1/15/26 2:15 PM, Amisha Chhajed wrote:
> Made the changes for other 2 places as well!
>
> I was also very curious about the presence of
> string_list_remove_duplicates in the original code, from my
> understanding string_list_insert already removed duplicates and
> string_list_remove_duplicates was still present with it.
So the string_list_remove_duplicates() calls were unnecessary with
string_list_insert(), but why is it safe to remove them now that you use
string_list_append() instead, which doesn't check for duplicates?
>
> On Thu, 15 Jan 2026 at 18:39, amisha <amishhhaaaa@gmail.com> 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.
>>
>> Signed-off-by: Amisha Chhajed <amishhhaaaa@gmail.com>
>> ---
>> builtin/sparse-checkout.c | 8 +++-----
>> 1 file changed, 3 insertions(+), 5 deletions(-)
>>
>> diff --git a/builtin/sparse-checkout.c b/builtin/sparse-checkout.c
>> index 15d51e60a8..edabe7cbd9 100644
>> --- a/builtin/sparse-checkout.c
>> +++ b/builtin/sparse-checkout.c
>> @@ -91,7 +91,7 @@ static int sparse_checkout_list(int argc, const char **argv, const char *prefix,
>>
>> 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);
>> @@ -289,11 +289,10 @@ static void write_cone_to_file(FILE *fp, struct pattern_list *pl)
>> if (!hashmap_contains_parent(&pl->recursive_hashmap,
>> pe->pattern,
>> &parent_pattern))
>> - string_list_insert(&sl, pe->pattern);
>> + string_list_append(&sl, pe->pattern);
>> }
>>
>> string_list_sort(&sl);
>> - string_list_remove_duplicates(&sl, 0);
>>
>> fprintf(fp, "/*\n!/*/\n");
>>
>> @@ -311,13 +310,12 @@ static void write_cone_to_file(FILE *fp, struct pattern_list *pl)
>> if (!hashmap_contains_parent(&pl->recursive_hashmap,
>> pe->pattern,
>> &parent_pattern))
>> - string_list_insert(&sl, pe->pattern);
>> + string_list_append(&sl, pe->pattern);
>> }
>>
>> strbuf_release(&parent_pattern);
>>
>> string_list_sort(&sl);
>> - string_list_remove_duplicates(&sl, 0);
>>
>> for (i = 0; i < sl.nr; i++) {
>> char *pattern = escaped_pattern(sl.items[i].string);
>> --
>> 2.51.0
>>
next prev parent reply other threads:[~2026-01-15 22:27 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
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 [this message]
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=fc14e0e5-93bc-4805-a20d-d2aa4eb87ddb@web.de \
--to=l.s.r@web.de \
--cc=amishhhaaaa@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=peff@peff.net \
--cc=stolee@gmail.com \
/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