From: Drew Adams <drew.adams@oracle.com>
To: John Yates <john@yates-sheets.org>, Robert Pluim <rpluim@gmail.com>
Cc: "Mattias Engdegård" <mattiase@acm.org>,
"Emacs developers" <emacs-devel@gnu.org>
Subject: RE: master 583cb26 2/3: Improve accuracy in string-replace description (bug#43598)
Date: Mon, 28 Sep 2020 09:49:47 -0700 (PDT) [thread overview]
Message-ID: <50bea60b-b70b-4a80-b85b-0c9283a033de@default> (raw)
In-Reply-To: <CAJnXXoi9GnigyD942dMghEttuGTVZ2EPrHtmbseOOg8FHA93CQ@mail.gmail.com>
> Okay. Then how about
>
> Return a string equal to @var{instring} with every occurence of
> @var{fromstring} replaced by @var{tostring}.
Return a new string equal...
____
But do we really need to say this now, for every function?
In the past nondestructive was the default (implicit), and
we called out destructive exceptions.
I'm not saying we shouldn't, especially if it just means
adding a "new" here or there. But if descriptions aren't
somewhat consistent then we risk increasing confusion,
rather than diminishing it. If we go out of our way to
say here that the returned string is a new one, will we
start saying that everywhere?
next prev parent reply other threads:[~2020-09-28 16:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200927124520.25321.62354@vcs0.savannah.gnu.org>
[not found] ` <20200927124522.BA20F207E0@vcs0.savannah.gnu.org>
2020-09-28 9:42 ` master 583cb26 2/3: Improve accuracy in string-replace description (bug#43598) Robert Pluim
2020-09-28 9:59 ` Mattias Engdegård
2020-09-28 11:09 ` Robert Pluim
[not found] ` <CAJnXXojjUAcRVmsZNWQ2j9rSDv76Y0od4yWfVg11k-Q2tf4NYA@mail.gmail.com>
2020-09-28 13:50 ` Robert Pluim
2020-09-28 16:36 ` John Yates
2020-09-28 16:49 ` Drew Adams [this message]
2020-09-28 16:55 ` Eli Zaretskii
2020-09-28 17:11 ` Drew Adams
2020-09-28 18:11 ` Eli Zaretskii
2020-09-28 22:36 ` John Yates
2020-09-28 22:47 ` Drew Adams
2020-09-29 2:35 ` Eli Zaretskii
2020-09-29 4:28 ` Drew Adams
2020-09-29 5:30 ` Eli Zaretskii
2020-09-29 15:28 ` Drew Adams
2020-09-29 2:37 ` Eli Zaretskii
2020-09-29 7:12 ` Robert Pluim
2020-09-29 14:26 ` Eli Zaretskii
2020-09-29 15:23 ` Robert Pluim
2020-09-29 16:02 ` Eli Zaretskii
2020-09-28 17:44 ` John Yates
2020-09-29 13:40 ` Lars Ingebrigtsen
2020-09-29 14:08 ` Mattias Engdegård
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=50bea60b-b70b-4a80-b85b-0c9283a033de@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=john@yates-sheets.org \
--cc=mattiase@acm.org \
--cc=rpluim@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.