From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Cc: kernel-janitors@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [cocci] [RFC] Choosing “semantics” better for SmPL script parts?
Date: Tue, 26 Aug 2025 09:30:17 +0200 [thread overview]
Message-ID: <f24b6e34-a9ae-4bfa-97f3-95503a732a88@web.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2508251521570.3563@hadrien>
> The default is exists for use with * and forall with transformation, with
> the reasoning for the latter being that when transformation occurs the
> trasformed code should be consistent.
Will corresponding development concerns be reconsidered in more detail?
Would you understand the source code search parameter “forall” in the way
that it expresses a stronger data processing requirement (than the setting
alternative “exists”)?
https://en.wikipedia.org/wiki/Universal_quantification
Is it known if such a quantification difference would influence software
run time characteristics in significant ways?
Regards,
Markus
prev parent reply other threads:[~2025-08-26 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 12:40 [cocci] [RFC] Choosing “semantics” better for SmPL script parts? Markus Elfring
2025-08-25 7:30 ` Markus Elfring
2025-08-25 13:23 ` Julia Lawall
2025-08-25 15:17 ` Markus Elfring
2025-08-26 7:30 ` Markus Elfring [this message]
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=f24b6e34-a9ae-4bfa-97f3-95503a732a88@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=julia.lawall@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.
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).