From: Alan Mackenzie <acm@muc.de>
To: Robert Pluim <rpluim@gmail.com>
Cc: michael_heerdegen@web.de, mattiase@acm.org,
Eli Zaretskii <eliz@gnu.org>,
61962@debbugs.gnu.org
Subject: bug#61962: 30.0.50; New trouble with symbols with positions
Date: Tue, 7 Mar 2023 15:46:24 +0000 [thread overview]
Message-ID: <ZAdcUMYa0rXCTAeM@ACM> (raw)
In-Reply-To: <87o7p4pt3p.fsf@gmail.com>
Hello, Robert.
On Tue, Mar 07, 2023 at 14:51:38 +0100, Robert Pluim wrote:
> >>>>> On Tue, 07 Mar 2023 15:13:40 +0200, Eli Zaretskii <eliz@gnu.org> said:
> >> Date: Tue, 7 Mar 2023 10:24:41 +0000
> >> Cc: Mattias Engdegård <mattiase@acm.org>,
> >> Eli Zaretskii <eliz@gnu.org>, 61962-done@debbugs.gnu.org
> >> From: Alan Mackenzie <acm@muc.de>
> >> I've now written safe-copy-tree, and committed it together with the fix
> >> in bytecomp.el to master.
> Eli> Next time when you post a patch and ask for comments, please allow
> Eli> some time for responses, including to those who might be in different
> Eli> time zones or have less free time on their hands. 13 hours you waited
> Eli> is definitely not enough.
> Yes. I was going to ask "why canʼt copy-tree be fixed to support
> circular lists instead of making people think about which function to
> use?".
safe-copy-tree is slower than copy-tree, probably _much_ slower, though
I haven't measured it. If there's no possibility of circular lists,
copy-tree will be far the better function to use.
> Robert
> --
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-03-07 15:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 16:18 bug#61962: 30.0.50; New trouble with symbols with positions Michael Heerdegen
2023-03-04 16:34 ` Eli Zaretskii
2023-03-04 21:39 ` Mattias Engdegård
2023-03-04 21:53 ` Michael Heerdegen
2023-03-05 16:04 ` Michael Heerdegen
2023-03-05 18:39 ` Alan Mackenzie
2023-03-05 19:41 ` Michael Heerdegen
2023-03-06 13:22 ` Alan Mackenzie
2023-03-07 0:29 ` Michael Heerdegen
2023-03-07 10:24 ` Alan Mackenzie
2023-03-07 13:13 ` Eli Zaretskii
2023-03-07 13:51 ` Robert Pluim
2023-03-07 15:46 ` Alan Mackenzie [this message]
2023-03-12 17:30 ` Mattias Engdegård
2023-03-12 20:42 ` Alan Mackenzie
2023-03-13 14:50 ` Eli Zaretskii
2023-03-14 12:31 ` Mattias Engdegård
2023-03-07 15:42 ` Alan Mackenzie
2023-03-07 15:15 ` Michael Heerdegen
2023-03-04 16:36 ` Eli Zaretskii
2023-03-04 16:47 ` Michael Heerdegen
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=ZAdcUMYa0rXCTAeM@ACM \
--to=acm@muc.de \
--cc=61962@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mattiase@acm.org \
--cc=michael_heerdegen@web.de \
--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 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).