GNU bug report logs - #64960
Documentation for copy-sequence

Previous Next

Full log

View this message in rfc822 format

From: uzibalqa <uzibalqa <at> proton.me>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: 64960 <at> debbugs.gnu.org, eliz <at> gnu.org
Subject: bug#64960: Documentation for copy-sequence
Date: Tue, 15 Aug 2023 00:43:49 +0000

Sent with Proton Mail secure email.

------- Original Message -------
On Tuesday, August 15th, 2023 at 11:46 AM, Michael Heerdegen <michael_heerdegen <at> web.de> wrote:


> uzibalqa uzibalqa <at> proton.me writes:
> 
> > Although I understand what it does, I om not sure if it would benefit
> > about some of the details we discussed.
> 
> 
> What in particular? A lot of the stuff discussed is a direct
> consequence of the copy being a new sequence object whose elements have
> not been copied. The manual tries to describe some implications.
> 
> Or should we try to find a better wording (to make more clear that
> "modify" doesn't mean "replace") - for what part(s)? What concretely
> would have helped you to understand that part of the manual better?

I found the following is mostly targeted at experienced users.

"The elements of a list, vector or record are not copied; they are
shared with the original."
 
Adding additional wording that it means that not everything is actually copied. 
Some aspects are actually reference values.  Meaning that if you change the
copied sequence, you could inadvertently change the original sequence.

> What parts of the documentation have you read so far?
> 
> 
> Thx,
> 
> Michael.
>

Previous Next

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