From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Emacs Development <emacs-devel@gnu.org>
Subject: RE: pcase-if-let?
Date: Wed, 28 Mar 2018 21:49:16 -0700 (PDT) [thread overview]
Message-ID: <ab45e04e-7f6b-42bf-8074-7f600ebe1225@default> (raw)
In-Reply-To: <871sg3ijgf.fsf@web.de>
> Yes, your are right with everything, the names are nonsense. I guess we
> are still in some kind of intermediate state - AFAIK Stefan hopes to
> integrate the pcase stuff more into Emacs innards some day. Dealing
> with these wide problems is not what I want to do here. For now, I just
> want to be consistent with the existing naming scheme.
I understand. And I really didn't expect name-changes at
this point. Just wanted to mention that the names of these
`pcase-*' things are not so helpful. It would have been
better to start off with better thinking about the names,
but we're past that now, it seems.
next prev parent reply other threads:[~2018-03-29 4:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 23:20 pcase-if-let? Michael Heerdegen
2018-03-28 23:54 ` pcase-if-let? Davis Herring
2018-03-29 0:21 ` pcase-if-let? Michael Heerdegen
2018-03-29 3:46 ` pcase-if-let? Michael Heerdegen
2018-03-29 4:14 ` pcase-if-let? Drew Adams
2018-03-29 4:39 ` pcase-if-let? Michael Heerdegen
2018-03-29 4:49 ` Drew Adams [this message]
2018-03-29 4:53 ` pcase-if-let? Stefan Monnier
2018-03-29 5:24 ` pcase-if-let? Michael Heerdegen
2018-03-29 11:59 ` pcase-if-let? Stefan Monnier
2018-03-30 1:52 ` pcase-if-let? Michael Heerdegen
2018-03-30 4:07 ` pcase-if-let? Drew Adams
2018-03-30 5:09 ` pcase-if-let? Michael Heerdegen
2018-03-30 15:07 ` pcase-if-let? Drew Adams
2018-03-30 23:22 ` pcase-if-let? Michael Heerdegen
2018-04-17 20:26 ` pcase-if-let? Nathan Moreau
2018-04-17 21:04 ` pcase-if-let? 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=ab45e04e-7f6b-42bf-8074-7f600ebe1225@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
/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).