From: Michael Heerdegen <michael_heerdegen@web.de>
To: "Štěpán Němec" <stepnem@gmail.com>
Cc: 35546@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>,
Tassilo Horn <tsdh@gnu.org>
Subject: bug#35546: 27.0.50; setf return value for new alist entries is wrong
Date: Mon, 13 Apr 2020 03:01:53 +0200 [thread overview]
Message-ID: <87r1wstczi.fsf@web.de> (raw)
In-Reply-To: <877dykdg6b.fsf@gmail.com> ("Štěpán Němec"'s message of "Sun, 12 Apr 2020 14:47:24 +0200")
Štěpán Němec <stepnem@gmail.com> writes:
> >> (lambda (v)
> >> + (macroexp-let2 nil v v
> >
> > Binding v to the value of v seems needlessly confusing. How about
> > renaming the lambda parameter to valexp or somthing like that?
>
> I kind of agree, although really, I wish that would be the most
> confusing part about gv.el. :-]
>
> I did it like that because 1. this practice seems pretty common in Emacs
> sources already, 2. it makes for the minimal change here.
It's a matter of taste. I read it like that `macroexp-let2' arranges
that the expression v refers to is evaluated only once, but not anything
else (if used correctly), so keeping the name is not more confusing than
torturing the reader with one more variable to remember in that already
not so easy to read code.
Apart from that debatable point the change looks reasonable to me.
Thanks,
Michael.
next prev parent reply other threads:[~2020-04-13 1:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 13:49 bug#35546: 27.0.50; setf return value for new alist entries is wrong Tassilo Horn
2019-05-07 11:19 ` Michael Heerdegen
2019-05-07 13:43 ` Michael Heerdegen
2019-05-07 14:58 ` npostavs
2019-05-07 15:56 ` Michael Heerdegen
2019-05-07 16:50 ` npostavs
2020-04-12 12:26 ` Štěpán Němec
2020-04-12 12:34 ` Noam Postavsky
2020-04-12 12:47 ` Štěpán Němec
2020-04-13 1:01 ` Michael Heerdegen [this message]
2020-08-19 10:34 ` Lars Ingebrigtsen
2020-08-25 16:16 ` Štěpán Němec
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=87r1wstczi.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=35546@debbugs.gnu.org \
--cc=npostavs@gmail.com \
--cc=stepnem@gmail.com \
--cc=tsdh@gnu.org \
/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).