From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 33199@debbugs.gnu.org, garreau@debbugs.gnu.org, galex-713@galex-713.eu
Subject: bug#33199: lambda forms are not self-quoting
Date: Tue, 30 Oct 2018 09:01:29 +0200 [thread overview]
Message-ID: <83in1jlxyu.fsf@gnu.org> (raw)
In-Reply-To: <87zhuwic9a.fsf@gmail.com> (message from Noam Postavsky on Mon, 29 Oct 2018 19:06:25 -0400)
> From: Noam Postavsky <npostavs@gmail.com>
> Date: Mon, 29 Oct 2018 19:06:25 -0400
> Cc: garreau@debbugs.gnu.org, alexandre <galex-713@galex-713.eu>
>
> Alexandre's recent post about pcase-lambda made me notice that lambda's
> docstring claims lambda forms are self-quoting. However, they are not:
>
> ;; -*- lexical-binding: t -*-
> (setq lexical-binding t) ; for *scratch*
>
> (lambda (x) (+ 1 x)) ;=> (closure (t) (x) (+ 1 x))
The doc string is still correct if lexical-binding is not in effect,
isn't it?
> From: Noam Postavsky <npostavs@gmail.com>
> Date: Mon, 29 Oct 2018 19:01:07 -0400
> Subject: [PATCH v1] Don't claim lambda forms are self-quoting
>
> * doc/lispref/functions.texi (Anonymous Functions):
> * lisp/subr.el (lambda): Don't say that a lambda form yields itself,
> under lexical binding it yields a closure object.
This removes useful information, IMO. I'd be much happier if we added
to the existing docs that lambda is not self-quoting in the
lexical-binding environment, and described (and explained) what does
happen in the lexical-binding environment.
Thanks.
next prev parent reply other threads:[~2018-10-30 7:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 23:06 bug#33199: lambda forms are not self-quoting Noam Postavsky
2018-10-30 7:01 ` Eli Zaretskii [this message]
2018-10-30 23:07 ` Noam Postavsky
2018-10-31 16:06 ` Eli Zaretskii
2018-11-09 1:26 ` Noam Postavsky
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=83in1jlxyu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33199@debbugs.gnu.org \
--cc=galex-713@galex-713.eu \
--cc=garreau@debbugs.gnu.org \
--cc=npostavs@gmail.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).