From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Cc: Michael Heerdegen <michael_heerdegen@web.de>
Subject: Re: [elpa] master 1d46de7 07/50: removed lexical-binding: t (confusing because not necessary)
Date: Sun, 08 Nov 2015 23:25:17 -0500 [thread overview]
Message-ID: <jwv37wfls6x.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <E1ZvdF6-0001UZ-U2@vcs.savannah.gnu.org> (Michael Heerdegen's message of "Mon, 09 Nov 2015 03:35:40 +0000")
> removed lexical-binding: t (confusing because not necessary)
In which sense is it confusing?
lexical-binding:t is expected to be "the standard" for new Elisp code.
It has various advantages such as giving more precise/detailed warnings,
have cleaner semantics, and even better performance (tho this is largely
hypothetical/theoretical for now).
Stefan
next parent reply other threads:[~2015-11-09 4:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151109033535.5602.4896@vcs.savannah.gnu.org>
[not found] ` <E1ZvdF6-0001UZ-U2@vcs.savannah.gnu.org>
2015-11-09 4:25 ` Stefan Monnier [this message]
2015-11-09 4:36 ` [elpa] master 1d46de7 07/50: removed lexical-binding: t (confusing because not necessary) Michael Heerdegen
[not found] ` <E1ZvdF4-0001To-Td@vcs.savannah.gnu.org>
2015-11-09 4:26 ` [elpa] master 0caf472 02/50: increased def value of on-screen-delay Stefan Monnier
2015-11-09 4:37 ` Michael Heerdegen
[not found] ` <E1ZvdFD-0001Ww-CQ@vcs.savannah.gnu.org>
2015-11-09 4:29 ` [elpa] master 350a979 23/50: add workaround for bug#16796 Stefan Monnier
2015-11-09 4:56 ` Michael Heerdegen
[not found] ` <E1ZvdF7-0001Uq-NT@vcs.savannah.gnu.org>
2015-11-09 4:33 ` [elpa] master c083518 09/50: added homepage to header Stefan Monnier
2015-11-09 4:41 ` Michael Heerdegen
[not found] ` <E1ZvdFM-0001aq-D8@vcs.savannah.gnu.org>
2015-11-09 4:35 ` [elpa] master d08c167 48/50: on-screen: merge from remote repo Stefan Monnier
2015-11-09 4:45 ` Michael Heerdegen
2015-11-09 4:59 ` Stefan Monnier
2015-11-09 5:13 ` Michael Heerdegen
2015-11-09 8:32 ` David Kastrup
2015-11-09 21:49 ` Richard Stallman
2015-11-09 21:52 ` 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=jwv37wfls6x.fsf-monnier+emacsdiffs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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.
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).