From: Drew Adams <drew.adams@oracle.com>
To: "Eli Zaretskii" <eliz@gnu.org>, "Štěpán Němec" <stepnem@gmail.com>
Cc: mattiase@acm.org, emacs-devel@gnu.org
Subject: RE: Regexp bytecode disassembler
Date: Sat, 21 Mar 2020 17:02:34 -0700 (PDT) [thread overview]
Message-ID: <080859bb-9569-48ad-9e75-e6853faa627a@default> (raw)
In-Reply-To: <c7304866-d309-4014-b6ac-73ab57ed171b@default>
> To me, `pcase' would be overkill here
... because it is more general. Like `cond', it
doesn't make clear that this is a simple case that
is exactly the case that `cl-case' handles.
Yes, the code in this case looks the same, whether
it is `pcase' or `cl-case', but the latter does
only this, so it's clear that only this is involved.
next prev parent reply other threads:[~2020-03-22 0:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 12:27 Regexp bytecode disassembler Mattias Engdegård
2020-03-20 12:58 ` Andreas Schwab
2020-03-20 14:34 ` Eli Zaretskii
2020-03-21 16:52 ` Mattias Engdegård
2020-03-21 19:19 ` Eli Zaretskii
2020-03-21 20:16 ` Štěpán Němec
2020-03-21 20:30 ` Eli Zaretskii
2020-03-21 20:40 ` Mattias Engdegård
2020-03-21 20:44 ` Štěpán Němec
2020-03-22 14:12 ` Eli Zaretskii
2020-03-22 14:43 ` Štěpán Němec
2020-03-22 16:55 ` Eli Zaretskii
2020-03-22 17:16 ` Štěpán Němec
2020-03-22 17:30 ` Eli Zaretskii
2020-03-22 18:34 ` Paul Eggert
2020-03-22 18:36 ` Dmitry Gutov
2020-03-21 20:50 ` Dmitry Gutov
2020-03-21 23:58 ` Drew Adams
2020-03-22 0:02 ` Drew Adams [this message]
2020-03-21 20:37 ` Mattias Engdegård
2020-03-22 3:28 ` Eli Zaretskii
2020-03-22 9:23 ` Mattias Engdegård
2020-03-22 10:37 ` Eli Zaretskii
2020-03-22 15:24 ` Mattias Engdegård
2020-03-22 17:06 ` Eli Zaretskii
2020-03-22 19:39 ` Mattias Engdegård
2020-03-22 20:12 ` Eli Zaretskii
2020-03-22 20:22 ` Corwin Brust
2020-03-20 15:39 ` Pip Cet
2020-03-21 16:56 ` Mattias Engdegård
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=080859bb-9569-48ad-9e75-e6853faa627a@default \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mattiase@acm.org \
--cc=stepnem@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 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.