From: Andrea Corallo via "Emacs development discussions." <emacs-devel@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, raman@google.com, emacs-devel@gnu.org
Subject: Re: News from the lexical world
Date: Mon, 12 Apr 2021 12:58:04 +0000 [thread overview]
Message-ID: <xjfblajek2r.fsf@sdf.org> (raw)
In-Reply-To: <83mtu33ea7.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Apr 2021 14:58:40 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andrea Corallo <akrl@sdf.org>
>> Cc: Eli Zaretskii <eliz@gnu.org>, raman@google.com, emacs-devel@gnu.org
>> Date: Mon, 12 Apr 2021 08:34:37 +0000
>>
>> 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?
Thanks
Andrea
next prev parent reply other threads:[~2021-04-12 12:58 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. [this message]
2021-04-12 13:23 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xjfblajek2r.fsf@sdf.org \
--to=emacs-devel@gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.