From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 18253@debbugs.gnu.org, tsugutomo.enami@jp.sony.com
Subject: bug#18253: 24.4.50; doc string of `remq': correct it per the doc of `remove'
Date: Tue, 26 Aug 2014 21:55:36 -0700 (PDT) [thread overview]
Message-ID: <ff28835d-5450-4201-bdaa-b92eff23a606@default> (raw)
In-Reply-To: <jwv61heboza.fsf-monnier+emacsbugs@gnu.org>
> > There is nothing wrong with letting users know the actual behavior.
>
> Of course there is: there is another possible behavior, which would
> generally be superior but which we didn't bother to implement (yet).
That's a pretty facile "of course". Of course you can document now
the behavior it has now, and if and when you ever change the behavior
you can update the doc accordingly. It's not like you just invented
`remq' - it's nearly as old as Lisp (at least as old as ZetaLisp).
And most (all other?) Lisps have given it the same behavior as `remove',
the only difference being to use `eq' instead of `equal'. IOW, they
systematically copy the sequence. All the more reason to let users
know that Emacs Lisp is exceptional in this regard.
It is this part of the Emacs definition that differs from the usual
definition, and makes Emacs `remq' unparallel with Emacs `remove':
(while (and (eq elt (car list)) (setq list (cdr list))))
next prev parent reply other threads:[~2014-08-27 4:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 14:59 bug#18253: 24.4.50; doc string of `remq': correct it per the doc of `remove' Drew Adams
2014-08-25 3:19 ` Christoph
2014-08-25 22:12 ` tsugutomo.enami
2014-08-25 22:37 ` Drew Adams
2014-08-26 18:34 ` Stefan Monnier
2014-08-26 18:57 ` Drew Adams
2014-08-27 3:18 ` Stefan Monnier
2014-08-27 4:55 ` Drew Adams [this message]
2014-08-27 5:31 ` tsugutomo.enami
2014-08-27 14:06 ` Drew Adams
2014-08-27 23:49 ` tsugutomo.enami
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff28835d-5450-4201-bdaa-b92eff23a606@default \
--to=drew.adams@oracle.com \
--cc=18253@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=tsugutomo.enami@jp.sony.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).