[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#64960: Documentation for copy-sequence
From: |
Drew Adams |
Subject: |
bug#64960: Documentation for copy-sequence |
Date: |
Mon, 31 Jul 2023 14:34:19 +0000 |
> > > > When I modify the copy, the original remains intact.
> > >
> > > No, if you modify an element of the copy, the corresponding element of
> > > the original is also changed. That's what "shared" means.
> >
> > Except for strings
>
> It is irrelevant what happens when you modify elements of a copied
> string because it is impossible. The statement is simply not applicable
> to strings. That's why the docstring only speaks of "list, vector or
> record".
>
> Note that substituting a character in a string is not the same as
> modifying the character. You are substituting a sequence element with
> another one and not modifying an element in that case.
>
> The same is true for the list (1 2 3) for example. Exactly the same
> situation as for a string: You can replace the number 2 in a copy with
> another one but you can't modify the number 2 in the list. Numbers and
> characters are not mutable.
Well put.
- bug#64960: Documentation for copy-sequence, (continued)
- bug#64960: Documentation for copy-sequence, uzibalqa, 2023/07/30
- bug#64960: Documentation for copy-sequence, Drew Adams, 2023/07/30
- bug#64960: Documentation for copy-sequence, uzibalqa, 2023/07/30
- bug#64960: Documentation for copy-sequence, Drew Adams, 2023/07/30
- bug#64960: Documentation for copy-sequence, uzibalqa, 2023/07/30
- bug#64960: Documentation for copy-sequence, Eli Zaretskii, 2023/07/30
- bug#64960: Documentation for copy-sequence, uzibalqa, 2023/07/30
- bug#64960: Documentation for copy-sequence, Michael Heerdegen, 2023/07/31
- bug#64960: Documentation for copy-sequence, uzibalqa, 2023/07/31
- bug#64960: Documentation for copy-sequence, Michael Heerdegen, 2023/07/31
- bug#64960: Documentation for copy-sequence,
Drew Adams <=