From: Augusto Stoffel <arstoffel@gmail.com>
To: 56875@debbugs.gnu.org
Subject: bug#56875: 29.0.50; [PATCH] Add thread-as macro
Date: Mon, 01 Aug 2022 19:06:53 +0200 [thread overview]
Message-ID: <87h72vq4eq.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
It has been noted many times that threading macros are not as useful in
Emacs Lisp because the APIs are not always consistent with regard to the
ordering of arguments. A “thread-as” macro on the lines of Clojure's
'as->' [1] would address this difficulty.
The signature of the Clojure macro is (as-> expr name & forms), which
looks a bit odd to me. Here I've changed this so the lexical variable
(name) comes before the initial value (expr).
Also, unlike thread-first and thread-last, in the attached version of
the macro there's no magic whereby an element of FORMS which is a
symbol, say fun, is turned into a function call, i.e. (fun name). In
other words, (thread-as x 1 1+) returns the symbol 1+. Clojure
behaves the same. I'm not necessarily against changing the macro so
that the above example returns 2, but I don't see a good reason to do
so either; for one thing, the example gives a byte-compilation warning
(unused lexical variable x).
[1]: https://clojure.github.io/clojure/clojure.core-api.html#clojure.core/as-%3E
[-- Attachment #2: 0001-Add-thread-as-macro.patch --]
[-- Type: text/x-patch, Size: 1183 bytes --]
From c044cf5891638cd0095db091e86303d683cf380d Mon Sep 17 00:00:00 2001
From: Augusto Stoffel <arstoffel@gmail.com>
Date: Mon, 1 Aug 2022 15:59:53 +0200
Subject: [PATCH] Add thread-as macro
* lisp/subr-x.el (thread-as): New macro.
---
lisp/emacs-lisp/subr-x.el | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/lisp/emacs-lisp/subr-x.el b/lisp/emacs-lisp/subr-x.el
index d5d7bfeb6f..916ed39a03 100644
--- a/lisp/emacs-lisp/subr-x.el
+++ b/lisp/emacs-lisp/subr-x.el
@@ -81,6 +81,23 @@ thread-last
threading."
(declare (indent 0) (debug thread-first))
`(internal--thread-argument nil ,@forms))
+
+(defmacro thread-as (var &rest forms)
+ "Successively bind VAR to the result of evaluating each of the FORMS.
+Return the last computed value.
+
+Example:
+ (thread-as x
+ 4
+ (- 10 x)
+ (/ x 2))
+ ⇒ 3"
+ (declare (indent 1))
+ (if forms
+ `(let ((,var ,(car forms)))
+ (thread-as ,var ,@(cdr forms)))
+ var))
+
(defsubst hash-table-empty-p (hash-table)
"Check whether HASH-TABLE is empty (has 0 elements)."
(zerop (hash-table-count hash-table)))
--
2.37.1
next reply other threads:[~2022-08-01 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 17:06 Augusto Stoffel [this message]
2022-08-02 3:40 ` bug#56875: 29.0.50; [PATCH] Add thread-as macro Richard Stallman
2022-08-02 6:57 ` Augusto Stoffel
2022-08-02 10:17 ` Lars Ingebrigtsen
2022-08-02 11:24 ` Eli Zaretskii
2022-08-02 12:56 ` Augusto Stoffel
2022-08-02 13:06 ` Eli Zaretskii
2022-08-03 3:47 ` Richard Stallman
2022-08-05 7:44 ` Augusto Stoffel
2022-09-02 10:46 ` Lars Ingebrigtsen
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=87h72vq4eq.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=56875@debbugs.gnu.org \
/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).