From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>,
Emacs Development <emacs-devel@gnu.org>
Cc: Nicolas Petton <nicolas@petton.fr>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: RE: thunk.el: Document that thunk-force == funcall?
Date: Tue, 17 Nov 2020 09:32:07 -0800 (PST) [thread overview]
Message-ID: <f80ba58e-b24b-4735-9c94-fda42b88cba7@default> (raw)
In-Reply-To: <871rgs3tdx.fsf@web.de>
> `thunk-force' is equivalent to `funcall' - thunks are functions. I
> wonder if we could/should officially document that fact?
>
> The background: because thunks are functions, one is allowed (and it is
> useful) to directly pass them to higher order functions e.g. as a test
> predicate, or bind them using `cl-flet', or `cl-letf' to a
> `symbol-function' place. Currently, the official solution would
> require
> to use a lambda wrapper.
>
> I have encountered this requirement several times (and using `thunk-
> let' was not always the solution) - thus my question.
FWIW, that makes sense to me. Why not tell users this?
It's fine to have an abstraction, but in Lisp it can
help to know the implementation, especially in a
straightforward case like this.
next prev parent reply other threads:[~2020-11-17 17:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 15:17 thunk.el: Document that thunk-force == funcall? Michael Heerdegen
2020-11-17 17:08 ` Tomas Hlavaty
2020-11-17 17:38 ` Michael Heerdegen
2020-11-17 18:09 ` Tomas Hlavaty
2020-11-17 21:07 ` Michael Heerdegen
2020-11-17 22:42 ` Tomas Hlavaty
2020-11-17 23:52 ` Stefan Monnier
2020-11-18 8:01 ` Tomas Hlavaty
2020-11-18 14:04 ` Stefan Monnier
2020-11-18 22:19 ` Tomas Hlavaty
2020-11-18 22:49 ` Stefan Monnier
2020-11-18 23:13 ` Tomas Hlavaty
2020-11-18 23:40 ` Stephen Leake
2020-11-18 9:04 ` Alfred M. Szmidt
2020-11-18 22:21 ` Tomas Hlavaty
2020-11-17 17:32 ` Drew Adams [this message]
2020-11-18 23:05 ` Tomas Hlavaty
2020-11-18 23:25 ` Tomas Hlavaty
2020-11-19 11:50 ` Mattias Engdegård
2020-11-19 18:14 ` Tomas Hlavaty
2020-11-19 17:18 ` Tomas Hlavaty
2020-11-19 9:49 ` Nicolas Petton
2020-11-17 21:51 ` Stefan Monnier
2020-11-25 14:16 ` Michael Heerdegen
2020-11-27 17:22 ` Michael Heerdegen
2020-12-17 4:37 ` Michael Heerdegen
2020-12-18 2:58 ` Adam Porter
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=f80ba58e-b24b-4735-9c94-fda42b88cba7@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
--cc=nicolas@petton.fr \
/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).