From: Dmitri Paduchikh <dpaduchikh@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Emacs developers <emacs-devel@gnu.org>,
Tino Calancha <tino.calancha@gmail.com>
Subject: Re: Anaphoric macros: increase visibility
Date: Sat, 14 Jan 2017 11:25:15 +0500 [thread overview]
Message-ID: <87h9529n04.fsf@gmail.com> (raw)
In-Reply-To: <87wpdyivvf.fsf@web.de> (Michael Heerdegen's message of "Fri, 13 Jan 2017 20:48:52 +0100")
Michael Heerdegen <michael_heerdegen@web.de> wrote:
> Tino Calancha <tino.calancha@gmail.com> writes:
>> Hi,
>>
>> I think anaphoric macros are a nice idiom; occasionally
>> they allow to write very concise and clear expressions.
>>
>> AFAICS, in the Emacs tree they are just introduced in ibuf-macs.el
>> (`ibuffer-aif', `ibuffer-awhen').
> We also already have `if-let' and `when-let' in "subr-x". They are like
> `aif' and `awhen' but you specify "it" explicitly.
This explicitness argument seems to be standard criticism against anaphoric
macros. But it's easy to fix by providing new names for these macros: if-it,
when-it, and so on. Besides being more explicit these names are more readable
than aif and awhen. Comparing if-it, when-it with if-let, when-let, it seems
clear that they represent different tradeoffs of simplicity vs. flexibility.
With best regards
Dmitri Paduchikh
next prev parent reply other threads:[~2017-01-14 6:25 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
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 [this message]
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=87h9529n04.fsf@gmail.com \
--to=dpaduchikh@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
--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).