From: Michael Heerdegen <michael_heerdegen@web.de>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Anaphoric macros: increase visibility
Date: Sun, 15 Jan 2017 01:39:10 +0100 [thread overview]
Message-ID: <87k29xqhqp.fsf@web.de> (raw)
In-Reply-To: alpine.DEB.2.20.1701141422370.4011@calancha-pc
Hi Tino,
> I wonder if it has sense to increase that family with a while-let
> (maybe others in case they are useful).
>
> From 60f26b512b191add12a0c91dc4d7ff95aba080d9 Mon Sep 17 00:00:00 2001
> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Sat, 14 Jan 2017 14:25:42 +0900
> Subject: [PATCH] * lisp/emacs-lisp/subr-x.el (while-let): New macro.
Maybe. I'm using `when-let' and `if-let' a lot, but I'm still not sure
in which direction we should develop this approach. I personally prefer
`when-let' and `if-let' over `awhen' and `aif'. I sometimes think that
`if-let*' would be a better name for `if-let' because bindings can refer
(and naturally most of the time do) refer to other bindings. I also
often think that `and-let' (or `and-let*' ...) would be a better name
for `when-let' (because the expressions for the bindings are `and'ed,
sot the whole thing feels more like `and' to me). And I often think
that it would be cool to couple them with pcase pattern matching. OTOH
we already have `pcase-let', but I can't get along with its semantics,
e.g.
(pcase-let ((`(,a ,b) '(1 2 3)))
(list a b))
==> (1 2)
although the pattern doesn't match.
Anyway, I think we should have an imagination of where the travel should
end before adding more *-let macros.
Regards,
Michael.
next prev parent reply other threads:[~2017-01-15 0:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 8:39 Anaphoric macros: increase visibility Tino Calancha
2017-01-13 19:48 ` Michael Heerdegen
2017-01-14 2:30 ` Rolf Ade
2017-01-14 2:48 ` Rolf Ade
2017-01-14 3:03 ` Noam Postavsky
2017-01-14 4:13 ` Richard Copley
2017-01-14 5:27 ` Tino Calancha
2017-01-15 0:39 ` Michael Heerdegen [this message]
2017-01-15 2:24 ` On the naming/behavior of {if, when}-let (was Re: Anaphoric macros: increase visibility) Mark Oteiza
2017-01-15 2:26 ` Anaphoric macros: increase visibility Michael Heerdegen
2017-01-15 10:24 ` Tino Calancha
2017-01-15 15:32 ` Stefan Monnier
2017-01-16 2:44 ` Tino Calancha
2017-01-16 3:59 ` Stefan Monnier
2017-01-14 6:25 ` Dmitri Paduchikh
2017-01-14 7:56 ` Tino Calancha
2017-01-14 10:15 ` Dmitri Paduchikh
2017-01-15 0:29 ` Michael Heerdegen
2017-01-15 2:03 ` Dmitri Paduchikh
2017-01-15 2:16 ` 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=87k29xqhqp.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=emacs-devel@gnu.org \
--cc=tino.calancha@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).