GNU bug report logs - #28627
24.5; doc of `copy-sequence'

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Drew Adams <drew.adams <at> oracle.com>
Subject: bug#28627: closed (Re: bug#28627: 24.5; doc of `copy-sequence')
Date: Sat, 30 Sep 2017 13:05:01 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#28627: 24.5; doc of `copy-sequence'

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 28627 <at> debbugs.gnu.org.

-- 
28627: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=28627
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 28627-done <at> debbugs.gnu.org
Subject: Re: bug#28627: 24.5; doc of `copy-sequence'
Date: Sat, 30 Sep 2017 16:04:31 +0300

> Date: Wed, 27 Sep 2017 13:40:06 -0700 (PDT)
> From: Drew Adams <drew.adams <at> oracle.com>
> 
> 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.

[Message part 3 (message/rfc822, inline)]

From: Drew Adams <drew.adams <at> oracle.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.5; doc of `copy-sequence'
Date: Wed, 27 Sep 2017 13:40:06 -0700 (PDT)

This (doc string) is not true for an empty sequence:

  "Return a copy of a list, vector, string or char-table."

This ((elisp) `Sequence Functions') is not true for an empty sequence:

     Storing a new element into the copy does not affect the original
     SEQUENCE, and vice versa.  However, the elements of the new
     sequence are not copies; they are identical (eq) to the elements
     of the original.  Therefore, changes made within these elements, as
     found via the copied sequence, are also visible in the original
     sequence.

This has not been true for an empty string since Emacs 23.  It is now
the case, for instance that (eq foo bar) here returns t:

(setq foo ""
      bar (copy-sequence foo))

(Before Emacs 23 it returned nil.)

Similarly, for [].  `copy-sequence' used to give you a new
empty-vector object.  Now it does not.

(However, before those changes the same thing did hold for the empty
list, (): copy-sequence did not return a new empty-list object.)

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.


In GNU Emacs 24.5.1 (i686-pc-mingw32)
 of 2015-04-11 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=3D/c/usr --host=3Di686-pc-mingw32'

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.