From: Stefan Kangas <stefankangas@gmail.com>
To: Andrea Corallo <akrl@sdf.org>, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, raman@google.com
Subject: Re: News from the lexical world
Date: Mon, 12 Apr 2021 08:23:31 -0500 [thread overview]
Message-ID: <CADwFkmmp2OJmS1j8Brpa_3sO3_X0BwMU9L_mRhdLiHig9v3fdg@mail.gmail.com> (raw)
In-Reply-To: <xjfblajek2r.fsf@sdf.org>
Andrea Corallo via "Emacs development discussions."
<emacs-devel@gnu.org> writes:
>>> But we can say that the native compiler works better on lexical code as
>>> on dynamic one just gives-up on any Lisp optimization :)
>>
>> Yes, this should definitely be documented.
>
> Where do you think would be the best place to document it?
This provides a real incentive to convert code to lexical-binding.
My vote would be for the ELisp manual, to give it as high visibility as
possible. Even better if we could also mention it in NEWS.
next prev parent reply other threads:[~2021-04-12 13:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 16:23 News from the lexical world Stefan Monnier
2021-02-12 16:49 ` Stefan Kangas
2021-02-13 11:06 ` Lars Ingebrigtsen
2021-02-12 21:37 ` Andrea Corallo via Emacs development discussions.
2021-02-15 19:18 ` Phillip Lord
2021-04-10 21:32 ` Stefan Monnier
2021-04-11 6:37 ` Lars Ingebrigtsen
2021-04-11 7:20 ` Andrea Corallo via Emacs development discussions.
2021-04-11 13:44 ` T.V Raman
2021-04-11 14:39 ` Stefan Monnier
2021-04-11 15:10 ` T.V Raman
2021-04-11 15:42 ` Eli Zaretskii
2021-04-11 16:34 ` Stefan Monnier
2021-04-12 8:34 ` Andrea Corallo via Emacs development discussions.
2021-04-12 11:58 ` Eli Zaretskii
2021-04-12 12:58 ` Andrea Corallo via Emacs development discussions.
2021-04-12 13:23 ` Stefan Kangas [this message]
2021-04-12 13:24 ` Eli Zaretskii
2021-04-26 6:47 ` Andrew Cohen
2021-04-26 10:08 ` Stefan Kangas
2021-04-26 12:06 ` Andrew Cohen
2021-04-26 16:06 ` Stefan Monnier
2021-04-26 23:31 ` Andrew Cohen
2021-04-29 22:06 ` Stefan Monnier
2021-04-30 0:17 ` Andrew Cohen
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=CADwFkmmp2OJmS1j8Brpa_3sO3_X0BwMU9L_mRhdLiHig9v3fdg@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=raman@google.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).