From: Michael Heerdegen <michael_heerdegen@web.de>
To: Philipp <p.stephani2@gmail.com>
Cc: 48585@debbugs.gnu.org
Subject: bug#48585: 28.0.50; Missing Edebug instrumentation for some 'if-let' variants
Date: Sat, 16 Jul 2022 01:15:06 +0200 [thread overview]
Message-ID: <87v8ry2cjp.fsf@web.de> (raw)
In-Reply-To: <m2pmxj2e43.fsf@Philipps-MBP.fritz.box> (Philipp's message of "Sat, 22 May 2021 13:37:48 +0200")
Philipp <p.stephani2@gmail.com> writes:
> Instrument the following definition using C-u C-M-x:
> (defun f (x) (if-let* (x) 1))
>
> Then, evaluate this form:
> (f 2)
>
> Edebug will step into 'f', but won't stop at 'x'.
>
> The problem lies in this part of the Edebug specification for 'if-let*':
>
> [&or symbolp (symbolp form) (form)]
>
> The 'symbolp' specification element causes Edebug to not instrument the
> 'x' symbol. However, the 'symbolp' specification is also necessary
> here; we couldn't just replace it with 'form' because that would make
> the branches overlap.
Dunno how bad an overlap is. I tried this:
(debug ((&rest [&or (symbolp form) (form) form])
body))
That lets instrumenting error:
| internal-macroexpand-for-load: Eager macro-expansion failure: (error
| "`let' bindings can have only one value-form" edebug-after 0 1 x)
Does that happen because `x` appears as binding _variable_ in the
expansion, and Ebebug messes with that? Then we would have a second
problem.
Michael.
prev parent reply other threads:[~2022-07-15 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 11:37 bug#48585: 28.0.50; Missing Edebug instrumentation for some 'if-let' variants Philipp
2022-07-15 10:16 ` Lars Ingebrigtsen
2022-07-16 22:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 0:13 ` Michael Heerdegen
2022-07-17 1:36 ` Michael Heerdegen
2022-07-17 2:04 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 15:45 ` Michael Heerdegen
2022-07-15 23:15 ` Michael Heerdegen [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=87v8ry2cjp.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=48585@debbugs.gnu.org \
--cc=p.stephani2@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).