unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Visuwesh <visuweshm@gmail.com>
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: Thu, 08 Dec 2022 16:20:11 +0200	[thread overview]
Message-ID: <83bkoe2d0k.fsf@gnu.org> (raw)
In-Reply-To: <87tu262gkq.fsf@gmail.com> (message from Visuwesh on Thu, 08 Dec 2022 18:33:17 +0530)

> From: Visuwesh <visuweshm@gmail.com>
> Cc: Akira Komamura <akira.komamura@gmail.com>,  59900@debbugs.gnu.org
> Date: Thu, 08 Dec 2022 18:33:17 +0530
> 
> [வியாழன் டிசம்பர் 08, 2022] Eli Zaretskii wrote:
> 
> > Could you please point out where does pcase.el uses 'map' in its
> > source?
> 
> Pcase matcher that uses the map library is in in map.el.
> See the (pcase-defmacro map (&rest args) line.

Thanks, but if the offending code is in map.el, then there should be
no problem for it to use functions or macros in map.el, right?

Or what am I missing?





  reply	other threads:[~2022-12-08 14:20 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 [this message]
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
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=83bkoe2d0k.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59900@debbugs.gnu.org \
    --cc=akira.komamura@gmail.com \
    --cc=visuweshm@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).