From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Subject: [cocci] Increasing awareness for short-circuit evaluation consequences by SmPL disjunctions?
Date: Wed, 5 Feb 2025 13:05:37 +0100 [thread overview]
Message-ID: <55fe2528-2405-4762-8e2c-f326810dc2ea@web.de> (raw)
Hello,
Disjunctions of the semantic patch language are using short-circuit evaluation.
It has got the consequence that the last element of the specified condition will
only be checked if all previous parts did not match. Such a technical detail
can lead to a recommended ordering of condition parts if you would like to care
for optimal run time characteristics of SmPL code.
The usage incidence might be unclear for involved case distinctions.
How do you think about to clarify possibilities any further for the reordering of
SmPL disjunction items?
Regards,
Markus
next reply other threads:[~2025-02-05 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 12:05 Markus Elfring [this message]
2025-02-05 12:11 ` [cocci] Increasing awareness for short-circuit evaluation consequences by SmPL disjunctions? Julia Lawall
2025-02-05 12:20 ` 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=55fe2528-2405-4762-8e2c-f326810dc2ea@web.de \
--to=markus.elfring@web.de \
--cc=cocci@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 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).