From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: master f515d658e5 1/2: Don't quote numbers in byte-run--set-*
Date: Sat, 18 Jun 2022 13:32:20 +0200 [thread overview]
Message-ID: <875yky2omz.fsf@gnus.org> (raw)
In-Reply-To: <jwv7d5f5f3d.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 17 Jun 2022 14:20:39 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Even though there's only one of these in-tree (at least I only got one
>> error when I originally had the code they way you have here), I was
>> thinking it might break out-of-tree code...
>
> That's a risk, indeed, but I couldn't find any such occurrences so far
> out there in the wild, hence my question.
The gains are pretty minuscule -- we'd avoid an `if' when processing
these declarations -- so I think I'd just leave it as is out of an
overabundance of caution.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-18 11:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165548588979.10920.4402229762078749924@vcs2.savannah.gnu.org>
[not found] ` <20220617171130.8EDECC01685@vcs2.savannah.gnu.org>
2022-06-17 17:58 ` master f515d658e5 1/2: Don't quote numbers in byte-run--set-* Stefan Monnier
2022-06-17 18:01 ` Stefan Monnier
2022-06-17 18:08 ` Lars Ingebrigtsen
2022-06-17 18:20 ` Stefan Monnier
2022-06-18 11:32 ` Lars Ingebrigtsen [this message]
2022-06-18 13:34 ` Stefan Monnier
2022-06-19 11:10 ` Lars Ingebrigtsen
2022-06-19 12:57 ` Basil L. Contovounesios
2022-06-19 13:15 ` Lars Ingebrigtsen
2022-06-19 16:19 ` Michael Heerdegen
2022-06-19 22:30 ` Lars Ingebrigtsen
2022-06-19 22:24 ` Stefan Monnier
2022-06-19 22:29 ` Lars Ingebrigtsen
2022-06-19 23:12 ` Stefan Monnier
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=875yky2omz.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@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.