From: tsugutomo.enami@jp.sony.com
To: Drew Adams <drew.adams@oracle.com>
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: Wed, 27 Aug 2014 14:31:01 +0900 [thread overview]
Message-ID: <tkra96qo5wq.fsf@sigxcpu.sm.sony.co.jp> (raw)
In-Reply-To: <ff28835d-5450-4201-bdaa-b92eff23a606@default>
Hi,
> 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.
How about to avoid the use of word `copy' to describe both `remq' and
`remove'?
The point of remq/remove is non-destructive operation. Whether it
returns a copy or not is not important. This matches CL's `remove'
definition. Actually, even the current `remove' implementation does not
return a copy when SEQ is not a list and there is nothing to remove.
If document explicitly says it returns a copy, reader might think
destructive operation can be performed on the result of both functions
while expecting original sequence unmodified.
enami.
next prev parent reply other threads:[~2014-08-27 5:31 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
2014-08-27 5:31 ` tsugutomo.enami [this message]
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=tkra96qo5wq.fsf@sigxcpu.sm.sony.co.jp \
--to=tsugutomo.enami@jp.sony.com \
--cc=18253@debbugs.gnu.org \
--cc=drew.adams@oracle.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).