From: Alan Mackenzie <acm@muc.de>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
Robert Pluim <rpluim@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
61962@debbugs.gnu.org
Subject: bug#61962: 30.0.50; New trouble with symbols with positions
Date: Sun, 12 Mar 2023 20:42:25 +0000 [thread overview]
Message-ID: <ZA45MbCu+62NgE7o@ACM> (raw)
In-Reply-To: <0166B01B-96AA-4A7D-B7F1-13A34C768C41@acm.org>
Hello, Mattias.
On Sun, Mar 12, 2023 at 18:30:51 +0100, Mattias Engdegård wrote:
> As promised earlier, I gave the safe-copy-tree code a good
> working-through. Testing revealed bugs but the new implementation
> shouldn't have them. It's internal for now as there seems to be no need
> for it elsewhere, which also permitted some gold-plating to be removed.
> The new code is also quite a bit faster.
I'm not at all happy with the changes you've made. You've transformed a
general purpose utility into a special purpose restricted one. It was me
that put the work in in the first place, and I wonder why. It was a
substantial amount of work, and it would appear to have been for nothing.
Why did you not talk to me about the changes you were intending to make?
You've simply overridden my judgment with your own in cutting the scope
of the new function down. Why? I thoroughly disagree with you that no
general purpose copy-tree is needed (I've lamented its lack before now),
and I thoroughly disagree with you that vectors and records need never be
copied.
You say there were bugs with my version. OK, thanks for correcting them,
but would you please identify exactly what the bugs were. How else am I
supposed to learn?
You say your new version is "quite a bit" faster. What does that mean?
A factor of 10? A factor of 2? 20%? 10%? How did you measure this
speed up, and what particular code change was responsible for it?
Thanks.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2023-03-12 20:42 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
2023-03-12 17:30 ` Mattias Engdegård
2023-03-12 20:42 ` Alan Mackenzie [this message]
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=ZA45MbCu+62NgE7o@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).