From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH] lib/string_map: simulate stable sorting
Date: Sun, 26 Nov 2023 18:53:50 +0200 [thread overview]
Message-ID: <y2lg469.8m90w6-too@iki.fi> (raw)
In-Reply-To: <20231125123352.1508578-1-david@tethera.net>
On Sat, Nov 25 2023, David Bremner wrote:
> qsort(3) does not promise stability, and recent versions of glibc have
> been showing more unstable behaviour [2]. Michael Gruber observed [1] test
> breakage due to changing output order for message properties.
>
> We provide a sorting order of (key,value) pairs that _looks_ stable by
> breaking ties based on value if keys are equal. Internally there may
> be some instability in the case of duplicate (key,value) pairs, but it
> should not be observable via the iterator API.
I don't know (from the visible context here) why this is needed, but I
can image it is useful, so
LGTM.
Tomi
>
> [1]: id:CAA19uiSHjVFmwH0pMC7WwDYCOSzu3yqNbuYhu3ZMeNNRh313eA@mail.gmail.com
> [2]: id:87msv3i44u.fsf@oldenburg.str.redhat.com
> ---
> lib/string-map.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/lib/string-map.c b/lib/string-map.c
> index e3a81b4f..99bc2ea2 100644
> --- a/lib/string-map.c
> +++ b/lib/string-map.c
> @@ -86,10 +86,14 @@ _notmuch_string_map_append (notmuch_string_map_t *map,
> static int
> cmppair (const void *pa, const void *pb)
> {
> + int cmp = 0;
> notmuch_string_pair_t *a = (notmuch_string_pair_t *) pa;
> notmuch_string_pair_t *b = (notmuch_string_pair_t *) pb;
>
> - return strcmp (a->key, b->key);
> + cmp = strcmp (a->key, b->key);
> + if (cmp == 0)
> + cmp = strcmp (a->value, b->value);
> + return cmp;
> }
>
> static void
> --
> 2.42.0
next prev parent reply other threads:[~2023-11-26 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 12:33 [PATCH] lib/string_map: simulate stable sorting David Bremner
2023-11-26 16:53 ` Tomi Ollila [this message]
2023-11-28 13:24 ` David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=y2lg469.8m90w6-too@iki.fi \
--to=tomi.ollila@iki.fi \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).