From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Can't compile `or' pcase pattern Date: Thu, 11 May 2017 22:29:56 -0400 Message-ID: References: <877f1nmlcf.fsf@drachen> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1494556224 22220 195.159.176.226 (12 May 2017 02:30:24 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 12 May 2017 02:30:24 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 12 04:30:18 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d90LR-0005cV-6a for ged-emacs-devel@m.gmane.org; Fri, 12 May 2017 04:30:17 +0200 Original-Received: from localhost ([::1]:51029 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d90LV-0002JY-7P for ged-emacs-devel@m.gmane.org; Thu, 11 May 2017 22:30:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36127) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d90LL-0002HP-MY for emacs-devel@gnu.org; Thu, 11 May 2017 22:30:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d90LH-0008MO-Q0 for emacs-devel@gnu.org; Thu, 11 May 2017 22:30:11 -0400 Original-Received: from [195.159.176.226] (port=58725 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d90LH-0008Kd-KK for emacs-devel@gnu.org; Thu, 11 May 2017 22:30:07 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1d90L9-0005JK-I6 for emacs-devel@gnu.org; Fri, 12 May 2017 04:29:59 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 19 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:O82Fg7Y1SHnGH3yFPWr2bpzvi/A= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:214799 Archived-At: > #+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 Looking at the definition of `l` I think you're pushing pcase a bit further than it can go. A bit like a DFA representation of a regexp can explode, a pcase's expansion can explode in some cases, and your `l` has all the tools needed to triggger such explosions. Maybe you can reduce the pain, by looking at the expansion and trying to see how pcase-mutually-exclusive-p could be improved to get a better result. Stefan