From: Garklein <garklein97@gmail.com>
To: Thierry Volpiatto <thievol@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: Elisp threading macros
Date: Wed, 28 Aug 2024 15:35:51 -0400 [thread overview]
Message-ID: <CALp=CknFg0QXwb2h7N=4mVWbcSR61LdQG=vG2FUAGJ2UOV=+oQ@mail.gmail.com> (raw)
In-Reply-To: <877cc0ec1t.fsf@posteo.net>
> And now we have no idea of what this code does, not speaking of the
> diverse ->, --> etc... that are a mystery.
To me, the `-some->' form is clearer than the `let'. (I am very happy
to learn about `when-let' though, useful!) I can easily read it left
to right, as if it were English and not code.
I don't see what's so bad about the names `->', `-->' etc. After all,
we commonly use functions with such cryptic names as `car', `cdr', and
`cons' :)
On Wed, Aug 28, 2024 at 2:25 PM Thierry Volpiatto <thievol@posteo.net> wrote:
>
> Garklein <garklein97@gmail.com> writes:
>
> > Hello,
> >
> > Would it be possible to have the dash.el macros `->', `->>', `-->',
> > and `-some->' in subr-x.el? I find them to be really useful, and would
> > love to see them in the base language.
>
> Personally, I have stopped using packages wrote with dash.el, the code is
> unreadable, at least for me.
> I hope we will not have to suffer of this in Emacs.
>
> > I know that `thread-first' and `thread-last' exist, but I find that my
> > eyes can recognize `->' and `->>' much easier. `-->' is really nice
> > for more complex threading.
> >
> > `-some->' is useful in cases like this:
> >
> > (let (foo (function-which-may-return-nil))
> > (when foo
> > (bar foo)))
> >
> > which can be rewritten, much cleaner, as
> >
> > (-some-> foo function-which-may-return-nil bar)
>
> And now we have no idea of what this code does, not speaking of the
> diverse ->, --> etc... that are a mystery.
>
> --
> Thierry
next prev parent reply other threads:[~2024-08-28 19:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 14:08 Elisp threading macros Garklein
2024-08-28 15:51 ` Robert Pluim
2024-08-28 16:42 ` Visuwesh
2024-08-28 17:13 ` Henrik Kjerringvåg
2024-08-28 15:55 ` Eli Zaretskii
2024-08-28 18:23 ` Basil L. Contovounesios
2024-08-31 12:50 ` Augusto Stoffel
2024-08-28 18:05 ` Philip Kaludercic
2024-08-28 19:43 ` Garklein
2024-08-28 19:54 ` Philip Kaludercic
2024-08-29 4:45 ` tomas
2024-08-30 7:30 ` Joost Kremers
2024-08-29 21:19 ` Sean Whitton
2024-08-29 21:46 ` Philip Kaludercic
2024-08-28 18:29 ` Thierry Volpiatto
2024-08-28 19:35 ` Garklein [this message]
2024-08-30 12:26 ` Rudolf Adamkovič
2024-08-30 13:12 ` Robert Pluim
2024-08-30 17:15 ` [External] : " Drew Adams
2024-09-01 16:43 ` Alfred M. Szmidt
2024-09-01 21:02 ` Drew Adams
2024-08-29 0:48 ` Po Lu
2024-08-29 5:19 ` Alfred M. Szmidt
2024-08-30 0:57 ` Garklein
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALp=CknFg0QXwb2h7N=4mVWbcSR61LdQG=vG2FUAGJ2UOV=+oQ@mail.gmail.com' \
--to=garklein97@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=thievol@posteo.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.