[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug#38708: eq vs eql in byte-compiled code

From: Andrea Corallo
Subject: Re: Bug#38708: eq vs eql in byte-compiled code
Date: Tue, 31 Dec 2019 15:51:09 +0000
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)

Pip Cet <address@hidden> 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.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]