A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://lists.gnu.org/archive/html/bug-gnu-emacs/2023-07/msg02082.html below:

bug#64960: Documentation for copy-sequence

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] 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.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4