GNU bug report logs - #65344
28.2; Unable to Edebug cl-flet form which uses argument destructuring

Previous Next

Package: emacs;

Reported by: Brandon Irizarry <brandon.irizarry <at> gmail.com>

Date: Wed, 16 Aug 2023 18:23:02 UTC

Severity: normal

Found in version 28.2

Fixed in version 30.1

Done: Gerd Möllmann <gerd.moellmann <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


Message #115 received at 65344 <at> debbugs.gnu.org (full text, mbox):

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Gerd Möllmann <gerd.moellmann <at> gmail.com>
Cc: brandon.irizarry <at> gmail.com,
 Mattias Engdegård <mattias.engdegard <at> gmail.com>,
 Michael Albinus <michael.albinus <at> gmx.de>, 65344 <at> debbugs.gnu.org
Subject: Re: bug#65344: 28.2; Unable to Edebug cl-flet form which uses
 argument destructuring
Date: Thu, 24 Aug 2023 03:14:52 +0200
Gerd Möllmann <gerd.moellmann <at> gmail.com> writes:

> Edebug then matches def-form with ((x y)) or (&rest x), and it finds it
> doesn't match.  I would have expected that this leads to backtracking
> and trying the second alternative of the &or, but that's not
> happening.

It's very similar to the originally reported problem.  As I said - maybe
look at `edebug-list-form' which is called in both cases and
intentionally inhibits backtracking, AFAIU.


> So, at the moment we're kinda stuck with the situation that local
> functions that look like local-functions with empty body, like
>
>   (cl-flet ((fn (...)))
>     ...)
>
> are not instrumented like the cl-flet extension case.  That's not a
> catastrphy, I guess.

Nothing in Emacs is a catastrophe (it's not the real world), but
debugging bugs are the least thing I want to cope with when debugging a
bug.

Michael.




This bug report was last modified 1 year and 261 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.