[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#36139: [PATCH] Make better use of the switch op in cond forms
From: |
Mattias Engdegård |
Subject: |
bug#36139: [PATCH] Make better use of the switch op in cond forms |
Date: |
Tue, 11 Jun 2019 13:12:26 +0200 |
10 juni 2019 kl. 17.38 skrev npostavs@gmail.com:
>
> Redefining eq, equal, memq, or member with defun or advice is already
> unreliable because they are translated to byte codes. eql and memql are
> not, so this patchset (specifically, the last 2 patches, I think) would
> make the situation a bit worse for those functions, in that it would
> prevent defun/advice override for eql and memql from applying in cond
> forms.
`eql' is already recognised for switch generation in cond forms today. More
generally, is redefinition of such fundamental built-ins really a serious
concern? The compiler assumes standard semantics for plenty of functions,
byte-codes or not. This is also mentioned in the manual.
bug#36139: [PATCH] Make better use of the switch op in cond forms, Stefan Monnier, 2019/06/18
bug#36139: [PATCH] Make better use of the switch op in cond forms, Stefan Monnier, 2019/06/18
bug#36139: [PATCH] Make better use of the switch op in cond forms, Stefan Monnier, 2019/06/18
bug#36139: [PATCH] Make better use of the switch op in cond forms, Stefan Monnier, 2019/06/18