From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Gregory Heytings <gregory@heytings.org>
Cc: 52063@debbugs.gnu.org, larsi@gnus.org,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#52063: 28.0.60; Confusing presentation of lambda
Date: Thu, 25 Nov 2021 03:09:15 +0300 [thread overview]
Message-ID: <m2czmpm6z8.fsf@fastmail.fm> (raw)
In-Reply-To: <664b6d0147ece2617779@heytings.org> (Gregory Heytings's message of "Wed, 24 Nov 2021 22:37:53 +0000")
On 24/11/2021 22:37 +0000, Gregory Heytings wrote:
>>> I'm annoyed by this misfeature. If it means nothing to you and others,
>>> so be it.
>>
>> I fully understand desire to see function values printed as much as
>> possible as their original source code, but it's hard to reconcile this
>> with the needs of clean semantics, efficient execution, good code
>> analysis, ...
>>
>
> AFAIU, the fundamental question here is: is "(closure (t) args body)"
> different in any way from "(lambda args body)"? If not, is there a good
> reason to use a "(closure (t)" instead of a "(lambda"?
>
> FWIW, I'm running an Emacs with the following patch right now, which
> apparently breaks a couple of edebug tests in make check. Apart from
> that, it seems that it doesn't change anything in the way Emacs behaves.
>
> [..]
Please let's not do that. We may need the context, that the function
originated as a closure, later for some reasons. Rather, I like what
Stefan said, that we should keep the reference to the source.
next prev parent reply other threads:[~2021-11-25 0:09 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 18:56 bug#52063: 28.0.60; Confusing presentation of lambda Eli Zaretskii
2021-11-24 7:35 ` Lars Ingebrigtsen
2021-11-24 12:48 ` Eli Zaretskii
2021-11-24 12:51 ` Lars Ingebrigtsen
2021-11-24 13:15 ` Eli Zaretskii
2021-11-24 13:31 ` Lars Ingebrigtsen
2021-11-24 14:38 ` Eli Zaretskii
2021-11-24 16:21 ` Lars Ingebrigtsen
2021-11-24 16:33 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-24 16:54 ` Eli Zaretskii
2021-11-24 17:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-24 17:44 ` Eli Zaretskii
2021-11-24 19:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-24 19:53 ` Eli Zaretskii
2021-11-24 20:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-24 20:14 ` Eli Zaretskii
2021-11-24 22:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-24 22:33 ` Jim Porter
2021-11-24 22:42 ` Jim Porter
2021-11-24 21:10 ` Eduardo Ochs
2021-11-24 16:40 ` Filipp Gunbin
2021-11-24 16:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-24 18:18 ` Filipp Gunbin
2021-11-24 19:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-24 19:41 ` Eli Zaretskii
2021-11-24 19:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-24 19:59 ` Eli Zaretskii
2021-11-24 20:23 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-24 22:37 ` Gregory Heytings
2021-11-25 0:09 ` Filipp Gunbin [this message]
2021-11-25 8:57 ` Michael Heerdegen
2021-11-25 13:09 ` Lars Ingebrigtsen
2021-11-25 14:08 ` Michael Heerdegen
2021-11-25 14:39 ` Gregory Heytings
2021-11-24 20:16 ` Philipp Stephani
2021-11-24 21:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-25 0:13 ` Filipp Gunbin
2021-11-25 13:15 ` Lars Ingebrigtsen
2021-11-25 19:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-25 19:56 ` Jim Porter
2021-11-26 12:28 ` Lars Ingebrigtsen
2021-11-26 12:26 ` Lars Ingebrigtsen
2021-11-26 13:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-26 13:22 ` Lars Ingebrigtsen
2021-11-26 13:26 ` Lars Ingebrigtsen
2021-11-26 14:57 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-26 15:00 ` Lars Ingebrigtsen
2021-11-26 16:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-27 14:17 ` Lars Ingebrigtsen
2021-11-27 15:28 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-29 13:54 ` Lars Ingebrigtsen
2021-11-29 17:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-30 14:07 ` Michael Heerdegen
2021-11-30 14:20 ` Lars Ingebrigtsen
2021-11-24 16:56 ` Eli Zaretskii
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=m2czmpm6z8.fsf@fastmail.fm \
--to=fgunbin@fastmail.fm \
--cc=52063@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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.