From: Michael Heerdegen <michael_heerdegen@web.de>
To: Emacs Development <emacs-devel@gnu.org>
Subject: Can't compile `or' pcase pattern
Date: Thu, 11 May 2017 18:04:00 +0200 [thread overview]
Message-ID: <877f1nmlcf.fsf@drachen> (raw)
[-- Attachment #1: Type: text/plain, Size: 2266 bytes --]
Hello,
Stefan, probably,
I have found a problem while working on el-search:
The following form F:
#+begin_src emacs-lisp
(el-search--matcher
'(or (l ^ defstruct object)
(l ^ (and (symbol "def") (or (pred macrop) (pred special-form-p))) object)))
#+end_src
should compile a lambda which contains a pcase form containing the given
`or' pattern:
#+begin_src emacs-lisp
(defun el-search--matcher (pattern &optional result)
(eval
(let ((expression (make-symbol "expression")))
`(el-search--with-additional-pcase-macros
(let ((byte-compile-debug t) ;make undefined pattern types raise an error
(warning-suppress-log-types '((bytecomp)))
(pcase--dontwarn-upats (cons '_ pcase--dontwarn-upats)))
(byte-compile (lambda (,expression)
(pcase ,expression
(,pattern ,(or result t))
(_ nil)))))))))
#+end_src
where `el-search--with-additional-pcase-macros' just temporarily adds
some pattern definitions to the pcase macro environment.
The problem is that the call of `el-search--matcher' in F takes over one
minute of time and then gives up with
| byte-compile-lapcode: Bytecode overflow
Similar cases also take extremely long also but don't cause an overflow.
AFAICT the expansion of the pattern does not produce extraordinarily
dumb code.
Even stranger: Calling `el-search--matcher' with any of the 2 patterns
inside the `or', i.e.,
#+begin_src emacs-lisp
(el-search--matcher
'(l ^ defstruct object))
#+end_src
and
#+begin_src emacs-lisp
(el-search--macroexpand
'(l ^ (and (symbol "def") (or (pred macrop) (pred special-form-p))) object))
#+end_src
instantly succeed.
Have I hit some weak point in the implementation of `pcase's `or'? Is
there some way to avoid this problem? Simplifying the semantics of `l'
seems to help a bit. But I would like to understand what the problem is
and how I could avoid it.
This is on master, but with emacs-25 I see same issue.
Quitting with debug-on-quit -> t doesn't look like there is an infinite
recursion while compiling or code walking (though the recursion depth is
not small).
For reference I attach the macroexpansion of the pattern in F.
Thanks,
Michael.
[-- Attachment #2: bug.el --]
[-- Type: application/emacs-lisp, Size: 11157 bytes --]
next reply other threads:[~2017-05-11 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 16:04 Michael Heerdegen [this message]
2017-05-12 2:29 ` Can't compile `or' pcase pattern Stefan Monnier
2017-05-13 14:14 ` Michael Heerdegen
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=877f1nmlcf.fsf@drachen \
--to=michael_heerdegen@web.de \
--cc=emacs-devel@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 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).