[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Code for cond*
From: |
João Távora |
Subject: |
Re: Code for cond* |
Date: |
Wed, 24 Jan 2024 11:30:03 +0000 |
On Wed, Jan 24, 2024 at 9:48 AM Stefan Kangas <stefankangas@gmail.com> wrote:
> We will end up with `pcase' for those that happen to prefer that, and
> `cond*' for those that happen to prefer that. For me, as a maintainer,
> I now have to know not one, but two relatively complex macros. While I
> realize that ELisp has been largely designed in an ad-hoc way,
> consciously introducing such needless proliferation does not strike me
> as a particularly good way to design a programming system.
+1 to everything said. And if cond* does show up somewhere, please
really implementing its interface in terms of pcase, whenever possible
(it seems it is possible in most if not all cases).
> In summary, I recommend installing `cond*' as a new package on GNU ELPA.
> This is a good way of exploring an alternative version of an existing
> macro.
+1 here, too.
João
- Re: Code for cond*, (continued)
Re: Code for cond*, Andrea Corallo, 2024/01/18
- Re: Code for cond*, João Távora, 2024/01/19
- Re: Code for cond*, Richard Stallman, 2024/01/20
- Re: Code for cond*, Adam Porter, 2024/01/21
- Re: Code for cond*, tomas, 2024/01/22
- Re: Code for cond*, Richard Stallman, 2024/01/23
- Re: Code for cond*, Po Lu, 2024/01/24
Re: Code for cond*, Stefan Kangas, 2024/01/24
Re: Code for cond*,
João Távora <=
Re: Code for cond*, João Távora, 2024/01/24
Re: Code for cond*, Po Lu, 2024/01/24
Re: Code for cond*, Ihor Radchenko, 2024/01/24
Re: Code for cond*, Po Lu, 2024/01/24
Re: Code for cond*, Ihor Radchenko, 2024/01/24
Re: Code for cond*, João Távora, 2024/01/24
Re: Code for cond*, Po Lu, 2024/01/24
Re: Code for cond*, Richard Stallman, 2024/01/26
Re: Code for cond*, Richard Stallman, 2024/01/26
Re: Code for cond*, Po Lu, 2024/01/24