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 11:57:12 -0700 (PDT) [thread overview]
Message-ID: <73ca6a31-03e0-493a-a4ae-5362597e3a70@default> (raw)
In-Reply-To: <jwv8umbksny.fsf-monnier+emacsbugs@gnu.org>
> It should just say that the returned list may share some elements
> with the original argument, but that no element was modified by
> side-effect.
Why would the question of whether an *element* was modified even come
up? That seems like a red herring, bound only to confuse people.
The question that arises for users is about sharing/modification of
the list structure, not elements. (Yes, of course an element can
itself be a list.)
There is nothing wrong with letting users know the actual behavior.
It would be helpful to provide the kind of information that Emacs
provides (and all Lisps provide) for `member': "The value is actually
the tail of LIST whose car is ELT."
But the main point - the point of the bug report, is that it is not
correct to say, as we say now, that `remq' "Returns LIST with all
occurrences of ELT removed." It does that only when all of the ELT
occurrences occur before any non-ELT occurrences.
next prev parent reply other threads:[~2014-08-26 18:57 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 [this message]
2014-08-27 3:18 ` Stefan Monnier
2014-08-27 4:55 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=73ca6a31-03e0-493a-a4ae-5362597e3a70@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 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.