From: Jonas Bernoulli <jonas@bernoul.li>
To: emacs-devel@gnu.org
Subject: #'quoting functions when they are used as identifiers
Date: Sun, 27 Mar 2022 14:27:03 +0200 [thread overview]
Message-ID: <87bkxrh97s.fsf@bernoul.li> (raw)
Hi,
I was wondering whether it is wrong per se to function-quote a
function-bound symbol if it serves as an argument to a function that
does not actually call the argument as a function but for which it
would never-the-less be a bug to be passed a symbol that isn't bound
as a function.
An imperfect example would be the arguments to `derived-mode-p'. I
don't plan to #'quote the arguments to that function but am considering
doing it for a few similar functions (from my `transient' package) for
which a prefect match exists between the name of the function and the
"symbol as an identifier".
The documentation says that ‘function’
returns FUNCTION-OBJECT without evaluating it. In this, it is
similar to ‘quote’. But unlike ‘quote’, it also serves as a note
to the Emacs evaluator and byte-compiler that FUNCTION-OBJECT is
intended to be used as a function. [...]
When FUNCTION-OBJECT is a symbol and the code is byte compiled, the
byte-compiler will warn if that function is not defined or might
not be known at run time.
I am considering adding #'quotes because I would like to get that
feedback from the byte-compiler. On the other hand, one might argue
that doing that is misleading to the human reader because the symbol
is not actually intended to be called as a function, it just has to be
a symbol that is fboundp, else there would be a bug (due to a typo or
renaming).
(I am not suggesting that we do this in Emacs.)
Thanks for your thoughts!
Jonas
next reply other threads:[~2022-03-27 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-27 12:27 Jonas Bernoulli [this message]
2022-03-27 18:58 ` #'quoting functions when they are used as identifiers Sean Whitton
2022-03-28 0:50 ` Jonas Bernoulli
2022-03-28 14:09 ` Stefan Monnier
2022-03-28 15:22 ` [External] : " Drew Adams
2022-03-29 18:26 ` Jonas Bernoulli
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=87bkxrh97s.fsf@bernoul.li \
--to=jonas@bernoul.li \
--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).