From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Merging results from parallel data processing?
Date: Sun, 10 May 2026 10:23:17 +0200 [thread overview]
Message-ID: <26e1d3aa-13f1-4e55-88d1-68b9d027ded0@web.de> (raw)
In-Reply-To: <e5a66d9c-5462-2f54-6abf-d2ec2cfd1d9@inria.fr>
>> * Would you like to distinguish item concatenation better from
>> the more advanced application of a merge algorithm?
>
> There is no more advanced applicationof the merge algorithm. There is
> only one merge algorithm. It does only one thing.
How do you think about to point the circumstances out under which this one
would be applied?
>> * Where is the information presented and explained that such data structures
>> would be involved here?
>
> What data structures?
Would you become more interested in the clarification of corresponding case distinctions?
>> I hope that data processing requirements can be clarified accordingly.
>
> The requirements are whatever requirements you have.
Do you care for the ordering of generated data anyhow?
Regards,
Markus
next prev parent reply other threads:[~2026-05-10 8:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 6:15 [cocci] Merging results from parallel data processing? Markus Elfring
2026-05-09 9:00 ` Julia Lawall
2026-05-09 16:38 ` Markus Elfring
[not found] ` <e5a66d9c-5462-2f54-6abf-d2ec2cfd1d9@inria.fr>
2026-05-10 8:23 ` Markus Elfring [this message]
[not found] ` <806afe75-8e1-17d8-dc3e-c2e33f4ab64@inria.fr>
2026-05-10 8:50 ` Markus Elfring
2026-05-10 9:07 ` Julia Lawall
2026-05-10 9:38 ` Markus Elfring
2026-05-10 11:42 ` Markus Elfring
[not found] ` <6614c14-3844-9774-24c3-e891ad57e9a@inria.fr>
2026-05-10 12:45 ` Markus Elfring
[not found] ` <44e0e8aa-f4f5-be2c-3956-a15d1989eec6@inria.fr>
2026-05-10 12:55 ` Markus Elfring
2026-05-10 13:00 ` Julia Lawall
2026-05-10 13:05 ` Markus Elfring
2026-05-10 17:34 ` loopily_
2026-05-11 15:33 ` Markus Elfring
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=26e1d3aa-13f1-4e55-88d1-68b9d027ded0@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=julia.lawall@inria.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.