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

Previous Next

Full log

Message #65 received at 64960 <at> debbugs.gnu.org (full text, mbox):

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

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?

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.