From: Michael Heerdegen <michael_heerdegen@web.de>
To: 61962@debbugs.gnu.org
Cc: acm@muc.de
Subject: bug#61962: 30.0.50; New trouble with symbols with positions
Date: Tue, 07 Mar 2023 16:15:24 +0100 [thread overview]
Message-ID: <87mt4osicz.fsf@web.de> (raw)
In-Reply-To: <ZAcQ6UrNEPUqtwsY@ACM> (Alan Mackenzie's message of "Tue, 7 Mar 2023 10:24:41 +0000")
Alan Mackenzie <acm@muc.de> writes:
> I've now written safe-copy-tree, and committed it together with the fix
> in bytecomp.el to master.
Thanks. Works well for me.
One note: the function fails for deeply nested structures because it
hits the recursion limit, e.g. for
#+begin_src emacs-lisp
(let ((my-list (list 1)))
(dotimes (i 10000)
(setq my-list (list my-list)))
(safe-copy-tree my-list))
#+end_src
> > I wonder now if other cases also suffer from the problem. What happens
> > when I call `eval' in a macro expander (i.e. while generating the macro
> > expansion, not in the result of an expansion)? And how does
> > `cl-eval-when' behave (this is actually a special case of the first
> > question) ?
>
> I think these are so far unsolved problems with the
> symbols-with-position mechanism - sometimes the s-w-p leaks out of macro
> contexts. Are you seeing this problem in real life?
So far, not that I knew, no. I'll keep my eyes open.
Thanks,
Michael.
next prev parent reply other threads:[~2023-03-07 15:15 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
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 [this message]
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=87mt4osicz.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=61962@debbugs.gnu.org \
--cc=acm@muc.de \
/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).