unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: mattias.engdegard@gmail.com, 70784@debbugs.gnu.org,
	monnier@iro.umontreal.ca
Subject: bug#70784: Abolish string resizing
Date: Tue, 07 May 2024 14:19:40 +0300	[thread overview]
Message-ID: <867cg5c1ir.fsf@gnu.org> (raw)
In-Reply-To: <87y18n3z9n.fsf@yahoo.com> (message from Po Lu on Mon, 06 May 2024 20:23:16 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: mattias.engdegard@gmail.com,  70784@debbugs.gnu.org,
>   monnier@iro.umontreal.ca
> Date: Mon, 06 May 2024 20:23:16 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > We are not going to abandon backward-compatibility considerations.
> > But refusing to discuss significant changes just because they have
> > compatibility issues is throwing the proverbial baby with the
> > bathwater.  Refusing changes is of course 110% backward-compatible,
> > but it has many disadvantages, to say the least.  Instead, we should
> > see how to keep compatibility, to the extent that we consider it
> > important, without blocking changes which could potentially help us
> > adopting new technologies and improving performance.
> 
> These principles are no doubt valid in general, but please consider what
> is the feature whose continued existence is being called into question!
> `(aset string n foo)' has been possible and countenanced for ages

Which is why this is not the feature that was suggested to be
abolished.  Please leave strawmen and red herrings out of this
discussion.  No one in their right mind will agree to removal of
'aset' for strings in general.

> the performance of strings has never been a source of user
> complaint.

You are very wrong.  String performance in Emacs is a known problem,
as evidenced by the fact that we recommend that Lisp programs use
buffers in preference to strings.

I'm not saying that going with this proposal will necessarily make the
problem less severe, just that your over-reaching argument is patently
incorrect.

> Without such a plain justification and a clear strategy for evaluating
> whether the results so produced meet expectations, there really is no
> detriment in categorically dismissing proposals to alter them, until
> such time, if ever, as these conditions are created.

No one said that we will accept this change based on performance
considerations without seeing some performance data.





  reply	other threads:[~2024-05-07 11:19 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-05 12:33 bug#70784: Abolish string resizing Mattias Engdegård
2024-05-05 14:04 ` Eli Zaretskii
2024-05-05 14:18   ` Mattias Engdegård
2024-05-05 15:23     ` Eli Zaretskii
2024-05-05 16:55       ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-05 17:10         ` Eli Zaretskii
2024-05-05 18:09           ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-05 18:14             ` Eli Zaretskii
2024-05-05 20:08               ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06  1:01                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06  6:02                   ` Gerd Möllmann
2024-05-08 23:25                     ` Richard Stallman
2024-05-08 23:24           ` Richard Stallman
2024-05-09  1:14             ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26  9:02       ` Stefan Kangas
2024-05-26  9:17         ` Eli Zaretskii
2024-05-26 18:03           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26 18:45             ` Eli Zaretskii
2024-05-27  3:42               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-28  2:23           ` Richard Stallman
2024-05-05 18:09     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-05 20:24       ` Mattias Engdegård
2024-05-05 21:14         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-11 15:20           ` Mattias Engdegård
2024-05-11 16:21             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-15 17:30             ` Mattias Engdegård
2024-05-15 17:47               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-15 19:35                 ` Mattias Engdegård
2024-05-25 11:24                 ` Mattias Engdegård
2024-05-25 11:37                   ` Eli Zaretskii
2024-05-25 13:01                     ` Mattias Engdegård
2024-05-06  0:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06  1:56   ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06 11:35     ` Eli Zaretskii
2024-05-06 12:29       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-07 11:13         ` Eli Zaretskii
2024-05-07 13:41           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06  2:41   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06  4:41     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06 10:57     ` Eli Zaretskii
2024-05-06 11:26   ` Eli Zaretskii
2024-05-06 12:23     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-07 11:19       ` Eli Zaretskii [this message]
2024-05-08 23:25   ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=867cg5c1ir.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=70784@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=mattias.engdegard@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).