From: Philipp <p.stephani2@gmail.com>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 48261@debbugs.gnu.org
Subject: bug#48261: 28.0.50; Optimize `eql' to `eq' for fixnums
Date: Sat, 8 May 2021 11:17:17 +0200 [thread overview]
Message-ID: <7C51F2BE-A271-492D-B0FF-18F586B071D0@gmail.com> (raw)
In-Reply-To: <1611E274-F759-4BBE-B136-FB6CDFD557B5@acm.org>
> Am 07.05.2021 um 11:23 schrieb Mattias Engdegård <mattiase@acm.org>:
> + (cl-every
>
> Are you sure this is a good idea? See comment in the beginning of bytecomp.el.
Yeah, good catch, will revert to the non-CL code before pushing.
next prev parent reply other threads:[~2021-05-08 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 17:20 bug#48261: 28.0.50; Optimize `eql' to `eq' for fixnums Philipp Stephani
2021-05-07 9:23 ` Mattias Engdegård
2021-05-07 15:24 ` bug#48261: [External] : " Drew Adams
2021-05-08 9:17 ` Philipp [this message]
2021-05-08 13:26 ` Mattias Engdegård
2021-05-16 12:48 ` Philipp Stephani
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=7C51F2BE-A271-492D-B0FF-18F586B071D0@gmail.com \
--to=p.stephani2@gmail.com \
--cc=48261@debbugs.gnu.org \
--cc=mattiase@acm.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).