GNU bug report logs - #70784
Abolish string resizing

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Po Lu <luangruo <at> yahoo.com>
Cc: mattias.engdegard <at> gmail.com, 70784 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca, drew.adams <at> oracle.com
Subject: bug#70784: Abolish string resizing
Date: Tue, 07 May 2024 14:13:30 +0300

> From: Po Lu <luangruo <at> yahoo.com>
> Cc: Drew Adams <drew.adams <at> oracle.com>,  mattias.engdegard <at> gmail.com,
>   70784 <at> debbugs.gnu.org,  monnier <at> iro.umontreal.ca
> Date: Mon, 06 May 2024 20:29:05 +0800
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > Which is why no one is proposing to make string immutable.  This is
> > not what this proposal is about, and Mattias made a point of saying
> > that explicitly.
> 
> The point is that CL string implementations are capable of modifying
> strings in such a manner as Mattias proposes to "abolish".  I presume
> some are implemented as Emacs's are, while others simply use a
> representation for multibyte strings where all characters are the same
> wide size (which incidentally there's nothing preventing Emacs from
> implementing).

That doesn't really matter.  "Other applications" do things that Emacs
doesn't necessarily want to do, or vice versa.  E.g., consider our
support for raw bytes in multibyte strings, which is quite unique.

What _would_ matter is if there are important use cases out there
where replacing one character by another character of a different
multibyte length.  So if you, or anyone else, can come up with such
situations (which are not made up specifically to argue here), please
do, because knowing about such situations would be useful to make this
discussion serious and based on facts.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.