From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 28627-done@debbugs.gnu.org
Subject: bug#28627: 24.5; doc of `copy-sequence'
Date: Sat, 30 Sep 2017 06:44:47 -0700 (PDT) [thread overview]
Message-ID: <22d8099a-7e00-4155-8979-2c42318c0788@default> (raw)
In-Reply-To: <<83h8vk49sw.fsf@gnu.org>>
> > The doc should make clear that there is only one empty-sequence object,
> > for each type of sequence. In particular, `copy-sequence' does not
> > create a new sequence object if the sequence is empty.
>
> Thanks. I didn't feel we should guarantee what we have in the current
> implementation, especially as describing all the details might be
> tedious (does "vectors" include bool-vector or doesn't it?). So I
> just added a vague statement that copying an empty object may yield
> the same object. I think this is enough for Lisp programmers to
> produce a valid and future-proof code.
I agree. What is important is to amend or remove the general
Statement that it always returns a copy of the sequence.
We could (or not) also stipulate that some sequence types have
only one empty-sequence object, which is what `copy-sequence'
returns for that sequence type.
next parent reply other threads:[~2017-09-30 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<f340c619-3b86-4687-af74-21a441c127c0@default>
[not found] ` <<83h8vk49sw.fsf@gnu.org>
2017-09-30 13:44 ` Drew Adams [this message]
2017-09-27 20:40 bug#28627: 24.5; doc of `copy-sequence' Drew Adams
2017-09-30 13:04 ` Eli Zaretskii
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=22d8099a-7e00-4155-8979-2c42318c0788@default \
--to=drew.adams@oracle.com \
--cc=28627-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).