From: Drew Adams <drew.adams@oracle.com>
To: "Štěpán Němec" <stepnem@gmail.com>, emacs-devel@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: RE: emacs-27 eebfb72 1/2: Document constant vs mutable objects better
Date: Sat, 18 Apr 2020 14:57:08 -0700 (PDT) [thread overview]
Message-ID: <35184b98-c5e4-470d-b65e-303e7e7d6c70@default> (raw)
In-Reply-To: <87wo6c5vxf.fsf@gmail.com>
> "mutable" and "safely mutable"/"mutating it is
> a good idea" should be distinguished.
Exactly.
> Similarly here. There are languages, Lisps even, that distinguish
> mutable and immutable strings/conses. In such languages, trying to
> mutate an immutable data structure leads to an error being signalled.
> Conflating "mutable" with "safely mutable" is IMO bound to induce
> confusion.
Ditto.
next prev parent reply other threads:[~2020-04-18 21:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200418200112.26900.1274@vcs0.savannah.gnu.org>
[not found] ` <20200418200114.85C8C20A2B@vcs0.savannah.gnu.org>
2020-04-18 21:24 ` emacs-27 eebfb72 1/2: Document constant vs mutable objects better Štěpán Němec
2020-04-18 21:57 ` Drew Adams [this message]
2020-04-19 20:37 ` Paul Eggert
2020-04-19 22:33 ` Štěpán Němec
2020-04-19 23:48 ` Paul Eggert
2020-04-20 0:18 ` Michael Heerdegen
2020-04-20 10:05 ` emacs-27 eebfb72 1/2: Document constant vs mutable objects better, Re: emacs-27 eebfb72 1/2: Document constant vs mutable objects better, " Štěpán Němec
2020-04-20 23:18 ` Michael Heerdegen
2020-04-22 17:54 ` Paul Eggert
2020-05-02 12:50 ` Štěpán Němec
2020-05-02 21:08 ` Paul Eggert
2020-04-20 0:16 ` Michael Heerdegen
2020-04-21 1:48 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=35184b98-c5e4-470d-b65e-303e7e7d6c70@default \
--to=drew.adams@oracle.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=stepnem@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.