[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Anaphoric macros: increase visibility
From: |
Noam Postavsky |
Subject: |
Re: Anaphoric macros: increase visibility |
Date: |
Fri, 13 Jan 2017 22:03:31 -0500 |
On Fri, Jan 13, 2017 at 9:30 PM, Rolf Ade <address@hidden> wrote:
>
> Michael Heerdegen <address@hidden> writes:
>> We also already have `if-let' and `when-let' in "subr-x". They are like
>> `aif' and `awhen' but you specify "it" explicitly.
>
> Since you mention them ... I probably miss something obvious but from
> looking at the documentation of if-let
>
> (if-let BINDINGS THEN &rest ELSE)
>
> and of when-let
>
> (when-let BINDINGS &rest BODY)
>
> I don't get, why there is a need for when-let?
>
Just like there is both `if' and `when', it's useful to have both
`if-let' and `when-let'.
- Anaphoric macros: increase visibility, Tino Calancha, 2017/01/13
- Re: Anaphoric macros: increase visibility, Michael Heerdegen, 2017/01/13
- Re: Anaphoric macros: increase visibility, Tino Calancha, 2017/01/14
- Re: Anaphoric macros: increase visibility, Michael Heerdegen, 2017/01/14
- On the naming/behavior of {if, when}-let (was Re: Anaphoric macros: increase visibility), Mark Oteiza, 2017/01/14
- Re: Anaphoric macros: increase visibility, Michael Heerdegen, 2017/01/14
- Re: Anaphoric macros: increase visibility, Tino Calancha, 2017/01/15
- Re: Anaphoric macros: increase visibility, Stefan Monnier, 2017/01/15
- Re: Anaphoric macros: increase visibility, Tino Calancha, 2017/01/15
- Re: Anaphoric macros: increase visibility, Stefan Monnier, 2017/01/15
Re: Anaphoric macros: increase visibility, Dmitri Paduchikh, 2017/01/14