From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
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 22:02:09 +0100 [thread overview]
Message-ID: <87lengs33i.fsf@web.de> (raw)
In-Reply-To: <83a63wz9a1.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 09 Dec 2022 21:06:46 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> > What specific question?
> The one I asked at the very beginning of this discussion:
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=59900#8
The same compiler error happens in emacs -Q if you compile a pcase
form that uses the map pattern and miss to require the map library,
e.g. compiling
#+begin_src emacs-lisp
(defun test (plist)
(pcase-let (((map :one (:two two)) plist))
(list one two)))
#+end_src
gives you
| Error: Unknown map pattern: (map :one (:two two))
but it's expected.
> It sounds like the bug is in the package which uses map.el, and that
> package is not part of Emacs.
Exactly.
But I still want to create a patch to support autoloading of the `map'
pattern in "map.el", this is a good idea.
Michael.
next prev parent reply other threads:[~2022-12-09 21:02 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lengs33i.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=59900@debbugs.gnu.org \
--cc=akira.komamura@gmail.com \
--cc=eliz@gnu.org \
/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.