From: Drew Adams <drew.adams@oracle.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: "Paul Eggert" <eggert@cs.ucla.edu>,
"João Távora" <joaotavora@gmail.com>,
"Pip Cet" <pipcet@gmail.com>, emacs-devel <emacs-devel@gnu.org>
Subject: FW: 31395511: "Don’t attempt to modify constant strings"
Date: Fri, 5 Jun 2020 18:34:50 -0700 (PDT) [thread overview]
Message-ID: <19454d0f-cf93-4fac-8a11-3f4ba5c52886@default> (raw)
In-Reply-To: bcde0400-8390-766f-2c19-d722a3097d99@yandex.ru
(Guess I forgot to use Reply All. Re-sending.)
> > [bug#40671] is about modifying literal objects and this
> > particular strangeness seems bigger than that.
>
> Later it goes deeper than that.
>
> > But that's a far cry from having two different manifestations
> > of `equal` such objects _be_ the same object, but only for
> > compiled code.
>
> That looks suboptimal to me too. I mean, it sounds like a sound
> optimization (to an extent), but I really wonder if it really buys us
> much in practice. And we're paying the price of not exactly obvious
> behavior.
Exactly the question - is it worth anything? Is it
worth the cost of unclear and less useful behavior?
next prev parent reply other threads:[~2020-06-06 1:34 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 21:52 31395511: "Don’t attempt to modify constant strings" João Távora
2020-06-03 22:41 ` Paul Eggert
2020-06-03 22:52 ` Pip Cet
2020-06-03 23:20 ` Paul Eggert
2020-06-03 23:20 ` Basil L. Contovounesios
2020-06-03 22:41 ` Pip Cet
2020-06-03 23:08 ` Basil L. Contovounesios
2020-06-03 23:31 ` Basil L. Contovounesios
2020-06-03 23:48 ` João Távora
2020-06-04 0:43 ` Paul Eggert
2020-06-04 1:19 ` Paul Eggert
2020-06-04 7:26 ` Pip Cet
2020-06-04 11:11 ` Basil L. Contovounesios
2020-06-04 19:46 ` Paul Eggert
2020-06-04 20:25 ` João Távora
2020-06-04 20:29 ` Paul Eggert
2020-06-04 21:21 ` Drew Adams
2020-06-04 20:43 ` Pip Cet
2020-06-04 21:27 ` Stefan Monnier
2020-06-04 21:42 ` Pip Cet
2020-06-04 23:10 ` Paul Eggert
2020-06-05 2:09 ` Clément Pit-Claudel
2020-06-05 6:44 ` Paul Eggert
2020-06-05 12:44 ` Stefan Monnier
2020-06-05 17:01 ` Drew Adams
2020-06-05 9:48 ` Pip Cet
2020-06-05 18:37 ` Paul Eggert
2020-06-04 22:33 ` Basil L. Contovounesios
2020-06-05 15:25 ` João Távora
2020-06-05 17:14 ` Dmitry Gutov
2020-06-05 23:19 ` João Távora
2020-06-05 23:32 ` Dmitry Gutov
2020-06-06 1:34 ` Drew Adams [this message]
2020-06-06 0:23 ` Drew Adams
2020-06-06 1:43 ` Paul Eggert
2020-06-06 4:06 ` Richard Stallman
2020-06-06 11:41 ` João Távora
2020-06-06 11:47 ` João Távora
2020-06-04 4:38 ` Pip Cet
2020-06-04 9:31 ` João Távora
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=19454d0f-cf93-4fac-8a11-3f4ba5c52886@default \
--to=drew.adams@oracle.com \
--cc=dgutov@yandex.ru \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=pipcet@gmail.com \
/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).