From: "Henrik Kjerringvåg" <hkjels@me.com>
To: Visuwesh <visuweshm@gmail.com>
Cc: Robert Pluim <rpluim@gmail.com>, Garklein <garklein97@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Elisp threading macros
Date: Wed, 28 Aug 2024 19:13:58 +0200 [thread overview]
Message-ID: <E19DA65B-8ED2-429E-8492-7EE7A8C5B72D@me.com> (raw)
In-Reply-To: <877cc0tx8t.fsf@gmail.com>
When-let is just functionally the same in the example provided. I think the point was actually about threading. I’m with Garklein on this subject. In my day job I program in Clojure and can attest to these threading macros being very valuable.
If Eldoc doesn’t work well with these macros, it sounds like some improvements can be made to Eldoc as well.
Sendt fra min iPhone
> 28. aug. 2024 kl. 18:43 skrev Visuwesh <visuweshm@gmail.com>:
> [புதன் ஆகஸ்ட் 28, 2024] Robert Pluim wrote:
>
>> Beauty is in the eye of the beholder:
>>
>> (when-let ((foo (function-which-may-return-nil)))
>> (bar foo))
>
> Not to mention, eldoc does not really work for these threading macros
> which is a real annoyance when trying to read code that heavily uses
> such macros.
next prev parent reply other threads:[~2024-08-28 17:13 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 [this message]
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
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
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=E19DA65B-8ED2-429E-8492-7EE7A8C5B72D@me.com \
--to=hkjels@me.com \
--cc=emacs-devel@gnu.org \
--cc=garklein97@gmail.com \
--cc=rpluim@gmail.com \
--cc=visuweshm@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).