From: Michael Heerdegen <michael_heerdegen@web.de>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: 28254@debbugs.gnu.org, Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#28254: 26.0.50; SRFI-2 and-let*
Date: Tue, 12 Sep 2017 20:44:11 +0200 [thread overview]
Message-ID: <87k213oiys.fsf@drachen> (raw)
In-Reply-To: <20170912130947.GA23119@holos.localdomain> (Mark Oteiza's message of "Tue, 12 Sep 2017 09:09:47 -0400")
Mark Oteiza <mvoteiza@udel.edu> writes:
> > Not really related to your change, but: Maybe we should additionally
> > say that THEN can refer to the bindings made in the VARLIST, but
> > ELSE to none, not even to those that resulted in non-nil values
> > before "failing".
>
> That's not true though--you can refer to the bindings in either branch:
Hmm, that feels strange. FWIW, all the scheme implementations I looked
at implemented it in a way that binding variables stops after the first
nil. OTOH I would expect that all bindings are only available from the
THIS branch (this is my personal opinion). In our case, we have
something third: always all bindings are visible in the ELSEs, e.g.
(let ((z 1))
(if-let* ((nil) (z 100))
(doesnt-matter)
z))
==> nil
That doesn't feel right.
I have two more questions:
In `internal--listify':
(defsubst internal--listify (elt)
"Wrap ELT in a list if it is not one.
If ELT is of the form ((EXPR)), listify (EXPR) with a dummy symbol."
(cond
((symbolp elt) (list elt elt))
((and (null (cdr elt))
(let ((form (car elt)))
(or (listp form) (atom form))))
(list (make-symbol "s") (car elt)))
(t elt)))
isn't (or (listp form) (atom form)) always true?
Secondly, in `internal--build-binding-value-form':
(defsubst internal--build-binding-value-form (binding prev-var)
"Build the conditional value form for BINDING using PREV-VAR."
(let ((var (car binding)))
(if (and (null (cdr binding)) (atom (car binding)) (not (symbolp (car binding))))
`(,var (and ,prev-var ,var))
`(,var (and ,prev-var ,(cadr binding))))))
how can it happen that (car binding) is an atom but not symbolp? And if
(car binding) == var is not a symbol, how does the returned binding make
sense?
Thanks,
Michael.
next prev parent reply other threads:[~2017-09-12 18:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 20:11 bug#28254: 26.0.50; SRFI-2 and-let* Mark Oteiza
2017-09-01 2:55 ` npostavs
2017-09-02 2:10 ` Mark Oteiza
2017-09-02 3:05 ` npostavs
2017-09-02 4:14 ` Mark Oteiza
2017-09-02 5:25 ` Michael Heerdegen
2017-09-02 13:36 ` Mark Oteiza
2017-09-02 18:41 ` Noam Postavsky
2017-09-03 17:48 ` Michael Heerdegen
2017-09-03 22:39 ` Mark Oteiza
2017-09-04 0:48 ` Mark Oteiza
2017-09-04 14:12 ` Michael Heerdegen
2017-09-05 3:47 ` Mark Oteiza
2017-09-05 15:04 ` Michael Heerdegen
2017-09-06 12:12 ` Michael Heerdegen
2017-09-06 13:06 ` Mark Oteiza
2017-09-06 19:04 ` Michael Heerdegen
2017-09-04 1:13 ` Mark Oteiza
2017-09-05 3:55 ` Mark Oteiza
2017-09-09 0:33 ` Mark Oteiza
2017-09-12 12:39 ` Michael Heerdegen
2017-09-12 13:09 ` Mark Oteiza
2017-09-12 18:44 ` Michael Heerdegen [this message]
2017-09-12 20:21 ` Mark Oteiza
2017-09-13 10:16 ` Michael Heerdegen
2017-09-13 11:48 ` Mark Oteiza
2017-09-13 16:46 ` Michael Heerdegen
2017-09-13 16:49 ` Mark Oteiza
2017-09-13 17:05 ` Michael Heerdegen
2017-09-13 17:28 ` Mark Oteiza
2017-09-13 17:49 ` Michael Heerdegen
2017-09-12 12:13 ` Michael Heerdegen
2017-09-12 14:29 ` Mark Oteiza
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=87k213oiys.fsf@drachen \
--to=michael_heerdegen@web.de \
--cc=28254@debbugs.gnu.org \
--cc=mvoteiza@udel.edu \
--cc=npostavs@users.sourceforge.net \
/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).