all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: npostavs@gmail.com
To: Drew Adams <drew.adams@oracle.com>
Cc: "Mattias Engdegård" <mattiase@acm.org>,
	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: Mon, 10 Jun 2019 11:38:57 -0400	[thread overview]
Message-ID: <85d0jlbgby.fsf@gmail.com> (raw)
In-Reply-To: <395efab3-80f6-4ff0-b754-9f58dd4af695@default> (Drew Adams's message of "Sat, 8 Jun 2019 08:38:54 -0700 (PDT)")

Drew Adams <drew.adams@oracle.com> writes:

> Or in a file that redefines `memq' or whatever using `defun' or similar?
>
> (But I guess the same problem exists in the current code, wrt `eq' etc.?)

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.





  parent reply	other threads:[~2019-06-10 15:38 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 [this message]
2019-06-11 11:12     ` Mattias Engdegård
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=85d0jlbgby.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=36139@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=mattiase@acm.org \
    --cc=monnier@iro.umontreal.ca \
    /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.