[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug#38708: eq vs eql in byte-compiled code
From: |
Stefan Monnier |
Subject: |
Re: Bug#38708: eq vs eql in byte-compiled code |
Date: |
Sat, 04 Jan 2020 14:55:40 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
> In other words, making bignums/flonums slower may seem to have no bad
> effects, until suddenly it has.
Agreed for flonums, but not for bignums: the bignum-replacements in
Emacs<27 were pretty inefficient, so I think we can use hash-consed
bignums without incurring a performance cost relative to Emacs-26.
IOW hash-cons'd bignums may be slower than "the best bignums we can
have", but they're still faster than the "the best bignums we used to
have".
Stefan
- Re: Bug#38708: eq vs eql in byte-compiled code, Mattias Engdegård, 2020/01/01
- Re: Bug#38708: eq vs eql in byte-compiled code, Stefan Monnier, 2020/01/01
- Re: Bug#38708: eq vs eql in byte-compiled code, Paul Eggert, 2020/01/02
- Re: Bug#38708: eq vs eql in byte-compiled code, Eli Zaretskii, 2020/01/02
- Re: Bug#38708: eq vs eql in byte-compiled code, Stefan Monnier, 2020/01/04
- Re: Bug#38708: eq vs eql in byte-compiled code, Paul Eggert, 2020/01/04
- Re: Bug#38708: eq vs eql in byte-compiled code, Stefan Monnier, 2020/01/04