[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#40968: 28.0.50; (apply nil)
From: |
Mattias Engdegård |
Subject: |
bug#40968: 28.0.50; (apply nil) |
Date: |
Thu, 7 May 2020 15:53:42 +0200 |
7 maj 2020 kl. 13.54 skrev Noam Postavsky <npostavs@gmail.com>:
> The obvious solution is just to leave the weird single arg form
> unoptimized. Otherwise, what about your earlier suggestion?
>
> (apply X) == (apply (car X) (cdr X))
Yes, we are under no obligation to optimise this case in any way.
> By the way, bytecomp-check-1 already ignores differences between error
> types. So the test case doesn't need a condition-case at all if we
> don't care about which particular error is signalled.
It seems to treat all errors as producing the value nil, but that should of
course be fixed.
bytecomp-tests.diff
Description: Binary data
- bug#40968: 28.0.50; (apply nil), (continued)