[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#64960: Documentation for copy-sequence
From: |
Eli Zaretskii |
Subject: |
bug#64960: Documentation for copy-sequence |
Date: |
Mon, 31 Jul 2023 05:21:44 +0300 |
> Date: Sun, 30 Jul 2023 19:20:45 +0000
> From: uzibalqa <uzibalqa@proton.me>
> Cc: 64960@debbugs.gnu.org
>
> > As the doc string says: the elements are not copied. You get a new
> > sequence whose elements are shared with the original one.
>
> So it returns a copy but elements are not copied. So what happens exactly ?
> You get a reference to the original ?
Yes.
> 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.
- bug#64960: Documentation for copy-sequence, (continued)
- 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, Dmitry Gutov, 2023/07/30
- bug#64960: Documentation for copy-sequence, uzibalqa, 2023/07/30
- 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 <=
- 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, 2023/07/31