From: Tomas Hlavaty <tom@logand.com>
To: Heime <heimeborgia@protonmail.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, help-gnu-emacs@gnu.org
Subject: Re: Advantage using mapc over dolist
Date: Mon, 02 Dec 2024 22:07:08 +0100 [thread overview]
Message-ID: <878qsxlrpf.fsf@neko.mail-host-address-is-not-set> (raw)
In-Reply-To: <xhTur-0KyPozR-Mf19ww2IUC--aAqNjNIF8pBc0X0vprLIXHDL-2ShH1oFSpjfMYWF8bN7dusgReaEasa61g41qKdgqZTySSEp84Eb1GQzU=@protonmail.com>
On Mon 02 Dec 2024 at 20:17, Heime <heimeborgia@protonmail.com> wrote:
> How can I find an example of exiting prematurely from mapc?
silly example:
(catch 'done
(let ((z 0))
(mapc (lambda (x)
(if (< x 10)
(setq z (+ z x))
(throw 'done z)))
'(3 5 7 13))))
You can search emacs sources for mapc.
I have a custom rg-emacs function for that:
(rg-emacs "mapc ")
which finds tempo-is-user-element function showing something
interesting:
(defun tempo-is-user-element (element)
"Try all the user-defined element handlers in `tempo-user-elements'."
;; Sigh... I need (some list)
(catch 'found
(mapc (lambda (handler)
(let ((result (funcall handler element)))
(if result (throw 'found result))))
tempo-user-elements)
(throw 'found nil)))
although in Common Lisp, I would avoid catch, throw and mapc and used
dolist with return or return-from instead:
(defun tempo-is-user-element (element)
(dolist (handler tempo-user-elements)
(let ((z (funcall handler element)))
(when z
(cl-return z)))))
This is more readable than the catch, mapc, throw code in Emacs.
Unfortunately, cl-return-from does not seems to be as convenient.
cl-return might do what I expect cl:return to be doing.
next prev parent reply other threads:[~2024-12-02 21:07 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-01 23:31 Advantage using mapc over dolist Heime via Users list for the GNU Emacs text editor
2024-12-02 6:26 ` Tomas Hlavaty
2024-12-02 18:30 ` Heime via Users list for the GNU Emacs text editor
2024-12-02 20:41 ` Tomas Hlavaty
2024-12-02 20:50 ` Jean Louis
2024-12-02 21:21 ` Tomas Hlavaty
2024-12-02 21:41 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 6:13 ` Jean Louis
2024-12-03 7:36 ` Tomas Hlavaty
2024-12-03 19:24 ` Jean Louis
2024-12-03 20:04 ` Tomas Hlavaty
2024-12-03 20:09 ` Jean Louis
2024-12-03 20:12 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 20:24 ` Jean Louis
2024-12-02 20:56 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 19:26 ` Jean Louis
2024-12-03 19:39 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 14:11 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-03 14:48 ` Tomas Hlavaty
2024-12-03 16:31 ` Stefan Monnier
2024-12-03 17:00 ` Alfred M. Szmidt
2024-12-03 17:24 ` Stefan Monnier
2024-12-03 19:27 ` Tomas Hlavaty
2024-12-03 19:35 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 14:59 ` Tomas Hlavaty
2024-12-03 15:40 ` Tomas Hlavaty
2024-12-03 15:57 ` Tomas Hlavaty
2024-12-03 17:11 ` Eli Zaretskii
2024-12-03 17:33 ` Tomas Hlavaty
2024-12-03 17:40 ` Eli Zaretskii
2024-12-03 17:55 ` Tomas Hlavaty
2024-12-03 18:05 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 18:57 ` Alfred M. Szmidt
2024-12-03 19:06 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 20:15 ` Tomas Hlavaty
2024-12-04 5:37 ` Alfred M. Szmidt
2024-12-03 19:42 ` Jean Louis
2024-12-03 19:54 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 20:11 ` Jean Louis
2024-12-03 16:47 ` Stefan Monnier
2024-12-03 18:01 ` Heime via Users list for the GNU Emacs text editor
2024-12-03 20:05 ` Jean Louis
2024-12-03 20:35 ` Tomas Hlavaty
2024-12-03 23:29 ` Stefan Monnier
2024-12-04 0:57 ` Heime via Users list for the GNU Emacs text editor
2024-12-04 2:20 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-12-03 19:38 ` Jean Louis
2024-12-04 4:56 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-12-02 6:59 ` Tassilo Horn
2024-12-02 10:12 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-12-02 17:03 ` Heime via Users list for the GNU Emacs text editor
2024-12-02 18:51 ` Tomas Hlavaty
2024-12-02 20:17 ` Heime via Users list for the GNU Emacs text editor
2024-12-02 21:07 ` Tomas Hlavaty [this message]
2024-12-03 13:19 ` Tomas Hlavaty
2024-12-02 21:15 ` [External] : " Drew Adams
2024-12-02 21:58 ` Tomas Hlavaty
2024-12-02 22:42 ` Drew Adams
2024-12-03 5:49 ` Tomas Hlavaty
2024-12-03 20:08 ` Lazy functional programming [was: Advantage using mapc over dolist] Drew Adams
2024-12-03 21:17 ` Tomas Hlavaty
2024-12-04 4:33 ` Advantage using mapc over dolist Michael Heerdegen
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=878qsxlrpf.fsf@neko.mail-host-address-is-not-set \
--to=tom@logand.com \
--cc=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
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).