[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Code for cond*
From: |
Stefan Monnier |
Subject: |
Re: Code for cond* |
Date: |
Thu, 25 Jan 2024 11:05:16 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
> (cond-let
> (:let var-for-rest value)
>
> Is there a reason why using a keyword here?
It was to "ensure" compatibility with existing `cond` code.
Also it was based on the premise that most `cond`s would *not* use it
since such code is mostly needed to replace things like:
(let (val)
(cond
[...]
((foo (setq var (bar)))
[...])
[...]))
And while such code does occur, it occurs only in a minority of `cond`
uses, so I thought it would be worthwhile for it to "stand out" so as
not to catch the reader by surprise.
Stefan
- Re: Code for cond*, (continued)
- RE: [External] : Re: Code for cond*, Drew Adams, 2024/01/24
- RE: [External] : Re: Code for cond*, Drew Adams, 2024/01/24
- Re: Code for cond*, Madhu, 2024/01/25
- Re: Code for cond*, Stefan Monnier, 2024/01/25
- Re: Code for cond*, JD Smith, 2024/01/25
- Re: Code for cond*, JD Smith, 2024/01/25
- Re: Code for cond*, Alfred M. Szmidt, 2024/01/25
- Re: Code for cond*, JD Smith, 2024/01/25
- Re: Code for cond*,
Stefan Monnier <=
- Re: Code for cond*, Alfred M. Szmidt, 2024/01/25
- Re: Code for cond*, Stefan Monnier, 2024/01/25
- Re: Code for cond*, JD Smith, 2024/01/25
- Re: Code for cond*, Richard Stallman, 2024/01/28
Re: Code for cond*, Richard Stallman, 2024/01/25
Re: Code for cond*, Richard Stallman, 2024/01/25