From: "Mattias Engdegård" <mattiase@acm.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 36139@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#36139: [PATCH] Make better use of the switch op in cond forms
Date: Tue, 11 Jun 2019 13:12:26 +0200 [thread overview]
Message-ID: <0D7CFFA0-FC7E-4D4E-A24C-4893776229B0@acm.org> (raw)
In-Reply-To: <85d0jlbgby.fsf@gmail.com>
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.
next prev parent reply other threads:[~2019-06-11 11:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 14:40 bug#36139: [PATCH] Make better use of the switch op in cond forms Mattias Engdegård
2019-06-08 15:38 ` Drew Adams
2019-06-09 8:38 ` Mattias Engdegård
2019-06-10 15:38 ` npostavs
2019-06-11 11:12 ` Mattias Engdegård [this message]
2019-06-11 11:25 ` Noam Postavsky
2019-06-18 12:46 ` Mattias Engdegård
2019-06-18 18:48 ` Stefan Monnier
2019-06-19 9:25 ` Mattias Engdegård
2019-06-18 18:56 ` Stefan Monnier
2019-06-18 19:03 ` Stefan Monnier
2019-06-19 9:30 ` Mattias Engdegård
2019-06-19 14:03 ` Mattias Engdegård
2019-06-28 20:51 ` Mattias Engdegård
2019-06-18 19:06 ` Stefan Monnier
2019-06-19 9:30 ` Mattias Engdegård
2019-06-18 19:19 ` Stefan Monnier
2019-06-19 10:14 ` Mattias Engdegård
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0D7CFFA0-FC7E-4D4E-A24C-4893776229B0@acm.org \
--to=mattiase@acm.org \
--cc=36139@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.