From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: akira.komamura@gmail.com, 59900@debbugs.gnu.org
Subject: bug#59900: 30.0.50; map pattern in pcase causes a byte-compile error
Date: Fri, 09 Dec 2022 09:12:17 +0200 [thread overview]
Message-ID: <837cz1125q.fsf@gnu.org> (raw)
In-Reply-To: <87k031nx6l.fsf@web.de> (message from Michael Heerdegen on Fri, 09 Dec 2022 03:11:14 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: Eli Zaretskii <eliz@gnu.org>, 59900@debbugs.gnu.org
> Date: Fri, 09 Dec 2022 03:11:14 +0100
>
> Akira Komamura <akira.komamura@gmail.com> writes:
>
> > I encountered similar errors in other libraries that contain a `map' pattern
> > inside a `pcase' form. It didn't happen until recently, when I updated Emacs
> > and
> > began to get those errors.
> >
> > So I wonder where's the place in the core Emacs sources
> > which causes the problem, and I couldn't find it. I'm probably
> > missing something.
>
> Maybe it started with
>
> | 85555ad3b79 ; Require map only during compilation
> | Philip Kaludercic <philipk@posteo.net> 2022-10-23
>
> Anyway, AFAIU currently compiling pcase forms with `map' patterns
> requires map.el to be currently loaded, and since you can't (and could
> not) rely on that, it's better to add
> (eval-when-compile (require 'map)).
Thanks, but all this still doesn't answer my questions,
unfortunately. You-all are describing something that I cannot wrap my
head around, because that basic question was not answered yet.
Would someone please take me through the problem step by step? ELI5,
OK?
next prev parent reply other threads:[~2022-12-09 7:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 7:50 bug#59900: 30.0.50; map pattern in pcase causes a byte-compile error Akira Komamura
2022-12-08 11:06 ` Eli Zaretskii
2022-12-08 13:03 ` Visuwesh
2022-12-08 14:20 ` Eli Zaretskii
2022-12-08 14:49 ` Visuwesh
2022-12-08 13:11 ` Akira Komamura
2022-12-09 2:11 ` Michael Heerdegen
2022-12-09 7:12 ` Eli Zaretskii [this message]
2022-12-09 7:58 ` Akira Komamura
2022-12-09 18:02 ` Michael Heerdegen
2022-12-09 19:06 ` Eli Zaretskii
2022-12-09 21:02 ` Michael Heerdegen
2022-12-10 1:01 ` Michael Heerdegen
2022-12-10 7:53 ` Eli Zaretskii
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=837cz1125q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59900@debbugs.gnu.org \
--cc=akira.komamura@gmail.com \
--cc=michael_heerdegen@web.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).