From: Andrea Corallo <akrl@sdf.org>
To: Pip Cet <pipcet@gmail.com>
Cc: mattiase@acm.org, eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: Bug#38708: eq vs eql in byte-compiled code
Date: Tue, 31 Dec 2019 15:51:09 +0000 [thread overview]
Message-ID: <xjf8smsfq8i.fsf@sdf.org> (raw)
In-Reply-To: <CAOqdjBc1YB5D2GHkJ4mf50HebdRa-hOUJr5jthKphu3-k87vOQ@mail.gmail.com> (Pip Cet's message of "Tue, 31 Dec 2019 15:07:11 +0000")
Pip Cet <pipcet@gmail.com> writes:
> The reason for this is that (eq 1.0 1.0) is optimized to nil before
> the constants are deduplicated, but other function calls use the
> deduplicated values.
If using eq (comparing words) on things that are not symbols has
unpredictable results I don't see the problem if this is true in the
run-time as in the compile-time.
I agree that having eq and eql equivalent would be probably too
expensive in terms of performance. Generally speaking I like to be able
to use 'eq' for what it is its classical definition.
--
akrl@sdf.org
next prev parent reply other threads:[~2019-12-31 15:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 15:07 Bug#38708: eq vs eql in byte-compiled code Pip Cet
2019-12-31 15:51 ` Andrea Corallo [this message]
2019-12-31 16:05 ` Mattias Engdegård
2019-12-31 17:38 ` Paul Eggert
2020-01-01 12:38 ` Mattias Engdegård
2020-01-02 8:38 ` Paul Eggert
2020-01-02 17:26 ` Mattias Engdegård
2020-01-04 19:55 ` Stefan Monnier
2020-01-22 10:56 ` Mattias Engdegård
2020-01-25 0:59 ` Paul Eggert
2020-01-01 15:45 ` Stefan Monnier
2020-01-02 7:52 ` Paul Eggert
2020-01-02 12:27 ` Pip Cet
2020-01-02 23:12 ` Paul Eggert
2020-01-02 13:48 ` Eli Zaretskii
2020-01-04 18:54 ` Stefan Monnier
2020-01-04 19:33 ` Paul Eggert
2020-01-04 19:49 ` 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
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=xjf8smsfq8i.fsf@sdf.org \
--to=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mattiase@acm.org \
--cc=pipcet@gmail.com \
/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).