From: Eli Zaretskii <eliz@gnu.org>
To: mattiase@acm.org
Cc: 42296@debbugs.gnu.org
Subject: bug#42296: 27.0.91; Correct manual entry for 'concat' w.r.t. allocation [PATCH]
Date: Thu, 09 Jul 2020 22:20:20 +0300 [thread overview]
Message-ID: <83pn94pkaz.fsf@gnu.org> (raw)
In-Reply-To: <83r1tkplnc.fsf@gnu.org> (message from Eli Zaretskii on Thu, 09 Jul 2020 21:51:19 +0300)
> Date: Thu, 09 Jul 2020 21:51:19 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 42296@debbugs.gnu.org
>
> That's not really what I asked for.
>
> And how does mutability enter the picture? We could say something
> about it (but then we'd have to be less terse), but that doesn't in
> any way replace the need to say that in many cases the value will be a
> new string, IMO.
Here's what I had in mind:
This function frequently, but not always, constructs a new string
that is not @code{eq} to any existing string. Lisp programs should
not rely on the result being a new string nor on it being @code{eq}
to an existing string.
When this function returns a string @code{eq] to another, changing
the result will also change that other string; to avoid that, use
@code{copy-sequence} on the result.
WDYT?
prev parent reply other threads:[~2020-07-09 19:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 15:54 bug#42296: 27.0.91; Correct manual entry for 'concat' w.r.t. allocation [PATCH] Mattias Engdegård
2020-07-09 17:31 ` Eli Zaretskii
2020-07-09 17:56 ` Mattias Engdegård
2020-07-09 18:51 ` Eli Zaretskii
2020-07-09 19:17 ` Mattias Engdegård
2020-07-09 19:24 ` Eli Zaretskii
2020-07-10 17:04 ` Mattias Engdegård
2020-07-10 18:08 ` Eli Zaretskii
2020-07-11 11:15 ` Mattias Engdegård
2020-07-11 11:52 ` Eli Zaretskii
2020-07-11 12:51 ` Mattias Engdegård
2020-07-11 13:07 ` Eli Zaretskii
2020-07-11 13:16 ` Mattias Engdegård
2020-07-11 13:37 ` Eli Zaretskii
2020-07-11 13:47 ` Mattias Engdegård
2020-07-11 16:17 ` Drew Adams
2020-07-12 3:03 ` Richard Stallman
2020-07-09 19:20 ` Eli Zaretskii [this message]
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=83pn94pkaz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42296@debbugs.gnu.org \
--cc=mattiase@acm.org \
/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).