all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Steven Allen <steven@stebalien.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 71398@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#71398: 30.0.50; Byte-compiling eat 0.9.4 stalls
Date: Fri, 07 Jun 2024 08:49:27 -0700	[thread overview]
Message-ID: <87a5jw92ig.fsf@stebalien.com> (raw)
In-Reply-To: <86y17hfgbv.fsf@gnu.org>


(CC Stefan because this appears to be caused by 16fc5b6c0c72464a75d9a84b754375662b3acec6)

Eli Zaretskii <eliz@gnu.org> writes:
> Thanks, but why do you think this is a bug in Emacs and not in eat?
> Did you report this to the eat developers?  If not, I suggest to do
> that first.

Ah, I should have included that context. This version of EAT used to
compile just fine, I only ran into an issue when I updated to master
yesterday.

On further investigation, this appears to be due to this [1] pcase. It
doesn't actually hang forever, it just gets exponentially slower for
each destructuring pattern with an internal operator like `or` or `and`.
E.g.:

    (`((,(or ?B ?e)) nil ((,n)))
     (eat--t-cur-down n))

I've tracked it down to 16fc5b6c0c72464a75d9a84b754375662b3acec6.
Reverting this commit makes `eat.el` compile instantly.

[1]: https://codeberg.org/akib/emacs-eat/src/commit/3a6f418f55d183b9d86f99c140caed4ba3d44f93/eat.el#L3534





  reply	other threads:[~2024-06-07 15:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 16:07 bug#71398: 30.0.50; Byte-compiling eat 0.9.4 stalls Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-07  5:54 ` Eli Zaretskii
2024-06-07 15:49   ` Steven Allen [this message]
2024-06-08 21:36     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-08 23:39       ` Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-09  3:40         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a5jw92ig.fsf@stebalien.com \
    --to=steven@stebalien.com \
    --cc=71398@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.