From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 69832@debbugs.gnu.org
Subject: bug#69832: 30.0.50; Should `subr-primitive-p` apply to special-forms?
Date: Sat, 16 Mar 2024 15:58:09 -0400 [thread overview]
Message-ID: <jwvv85mez60.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <86il1m55bk.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 16 Mar 2024 21:45:19 +0200")
>> I can see two ways to fix that:
>>
>> - Introduce a new type, says `subr-function(-p)` which returns non-nil
>> if and only if the argument is a built-in primitive *and* a function.
>>
>> - Change the implementation of `subr-primitive-p` to match its docstring.
>>
>> The patch below does the second (including changing the only place
>> I found that wants the current semantics.
>>
>> Comments? Objections?
>
> Why take the path of a breaking change instead of the non-breaking
> alternative?
- It can be considered as a bug fix (to make the code match its doc).
- If we introduce `subr-function-p`, then `subr-primitive-p` is only
"useful" at one place any more, and we can trivially rewrite the code to
avoid it, so we could get rid of it.
- These functions are used very rarely, the majority is in core files,
and the rest is mostly used to generate human-facing descriptions
so the risk of breakage is low and the kind of breakage is likely to
have a low impact.
Stefan
next prev parent reply other threads:[~2024-03-16 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 19:30 bug#69832: 30.0.50; Should `subr-primitive-p` apply to special-forms? Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-16 19:45 ` Eli Zaretskii
2024-03-16 19:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-03-16 20:17 ` Eli Zaretskii
2024-03-16 23:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-17 6:01 ` Eli Zaretskii
2024-03-17 21:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=jwvv85mez60.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=69832@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.