From: Marcin Borkowski <mbork@mbork.pl>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Are "proper" closures used in Emacs sources?
Date: Tue, 12 Jan 2021 14:50:24 +0100 [thread overview]
Message-ID: <875z42s1r3.fsf@mbork.pl> (raw)
Hi all,
it's been quite some time since lexical binding was introduced to
Elisp. Apart from possible optimizations and being less error-prone, it
allows for all the cool tricks with closures. Are there any places in
Emacs core where "proper" closures are actually used? (By "proper",
I mean closures with non-empty lexical environment, actually using said
environment.)
TIA,
--
Marcin Borkowski
http://mbork.pl
next reply other threads:[~2021-01-12 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 13:50 Marcin Borkowski [this message]
2021-01-12 15:43 ` Are "proper" closures used in Emacs sources? tomas
2021-01-12 15:56 ` Zhu Zihao
2021-01-12 15:57 ` Stefan Monnier
2021-01-12 16:48 ` Andrea Corallo via Emacs development discussions.
2021-01-12 17:22 ` Stefan Monnier
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=875z42s1r3.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=emacs-devel@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).