From: Eli Zaretskii <eliz@gnu.org>
To: Gemini Lasswell <gazally@runbox.com>
Cc: 31052@debbugs.gnu.org
Subject: bug#31052: 26.0.91; Improve documentation of inline-letevals
Date: Thu, 05 Apr 2018 12:54:51 +0300 [thread overview]
Message-ID: <834lkq2d1w.fsf@gnu.org> (raw)
In-Reply-To: <87vad6zyls.fsf@runbox.com> (message from Gemini Lasswell on Wed, 04 Apr 2018 10:10:39 -0700)
> From: Gemini Lasswell <gazally@runbox.com>
> Cc: 31052@debbugs.gnu.org
> Date: Wed, 04 Apr 2018 10:10:39 -0700
>
> > How about if you first tell informally what information is missing
> > from the original text, and then we see how to augment that by adding
> > the missing bits?
>
> The main question the existing documentation doesn't answer is what the
> purpose of inline-letevals is and why it should be used instead of 'let'.
OK, but in that case we need only add a single sentence:
This provides a convenient way to ensure that the arguments to an
inlined function are evaluated exactly once, as well as to create
local variables.
> The misleading part of the existing documentation is that it describes
> inline-letevals as similar to 'let' without mentioning that it does a
> completely different thing to symbols in the binding list.
The only part of your change that I perceive as related to this is the
following sentence:
When an element of @var{bindings} is just a symbol @var{var}, the
result of evaluating @var{var} is re-bound to @var{var}.
Is this what caused you to say it "does a completely different thing
to symbols in the binding list"? Or did I misunderstand?
Thanks.
next prev parent reply other threads:[~2018-04-05 9:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 0:33 bug#31052: 26.0.91; Improve documentation of inline-letevals Gemini Lasswell
2018-04-04 6:45 ` Eli Zaretskii
2018-04-04 13:18 ` Andy Moreton
2018-04-04 14:06 ` Eli Zaretskii
2018-04-05 1:12 ` Stefan Monnier
2018-04-04 17:10 ` Gemini Lasswell
2018-04-05 9:54 ` Eli Zaretskii [this message]
2018-04-06 20:29 ` Gemini Lasswell
2020-08-22 15:59 ` Lars Ingebrigtsen
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=834lkq2d1w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31052@debbugs.gnu.org \
--cc=gazally@runbox.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).