GNU bug report logs - #70784
Abolish string resizing

Previous Next

Package: emacs;

Reported by: Mattias EngdegÄrd <mattias.engdegard <at> gmail.com>

Date: Sun, 5 May 2024 12:35:02 UTC

Severity: wishlist

Full log


Message #47 received at 70784 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Po Lu <luangruo <at> yahoo.com>, Mattias EngdegÄrd
 <mattias.engdegard <at> gmail.com>
Cc: "70784 <at> debbugs.gnu.org" <70784 <at> debbugs.gnu.org>,
 Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: RE: [External] : bug#70784: Abolish string resizing
Date: Mon, 6 May 2024 01:56:27 +0000
> Is it only I who am tired of these proposals for complete upheavals
> that, somehow, Emacs has fared just fine without, for generations past?

You're not the only one.

> Backwards-compatibility is an obligation that cannot be
> evaded by means of warnings, which instead serve to annoy
> and antagonize users, whose only wish is that Emacs leave
> them in peace.

Happy to hear that POV.
___

Wrt mutable strings: Consider that Common Lisp, whose
implementations can be very performant, has always had
mutable strings.  I'd even wager that no one ever argued
that its strings shouldn't be mutable.  Inconceivable.

Yes, CL strings are vectors (thus arrays, thus sequences)
of chars, so they're different from Elisp strings.  As
such, you can use sequence functions on them (including
destructive functions such as nreverse).

On the other hand, Elisp strings can have text properties.
(Let's please not hear a proposal to remove that feature
as well, in the name of immutability or performance.)

This bug report was last modified 141 days ago.

Previous Next


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