From: Sam Steingold <sds@gnu.org>
To: emacs-devel@gnu.org
Subject: byte-opt.el vs declare
Date: Tue, 26 Jul 2022 15:57:39 -0400 [thread overview]
Message-ID: <lz4jz31wb0.fsf@3c22fb11fdab.ant.amazon.com> (raw)
I thought that byte-opt was intended to set `pure'. `side-effect-free'
&c properties for functions that are defined in C and functions defined
in Lisp should get these from `declare'.
However, I see that, e.g., `xor' uses `declare' but `string-prefix-p' is
listed in byte-opt and does not have a declaration.
What is the official policy?
Thank you.
--
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.2113
http://childpsy.net http://calmchildstories.com http://steingoldpsychology.com
https://iris.org.il https://www.memritv.org https://ffii.org
Failure is not an option. It comes bundled with your Microsoft product.
next reply other threads:[~2022-07-26 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 19:57 Sam Steingold [this message]
2022-07-27 8:31 ` byte-opt.el vs declare Mattias Engdegård
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=lz4jz31wb0.fsf@3c22fb11fdab.ant.amazon.com \
--to=sds@gnu.org \
--cc=emacs-devel@gnu.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://git.savannah.gnu.org/cgit/emacs.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).