[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#64960: Documentation for copy-sequence
From: |
Michael Heerdegen |
Subject: |
bug#64960: Documentation for copy-sequence |
Date: |
Tue, 01 Aug 2023 05:56:56 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
uzibalqa <uzibalqa@proton.me> writes:
> > 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.
>
> This is the difficult part. You have a copy of a list and you can swap
> elements but not make new ones. So what you share is the address, where
> element 2 say uses the address of element 3.
>
> All this copy-sequence is then quite restrictive in its capabilities.
> It does not allow much changes.
I must admit that I don't understand this answer. What does "can't make
new elements" mean? "Does not allow changes"...you lost me here.
Michael.
- bug#64960: Documentation for copy-sequence, (continued)
- bug#64960: Documentation for copy-sequence, Dmitry Gutov, 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, 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 <=
- bug#64960: Documentation for copy-sequence, Drew Adams, 2023/07/31