From: Mark Oteiza <mvoteiza@udel.edu>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 28254-done@debbugs.gnu.org,
Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#28254: 26.0.50; SRFI-2 and-let*
Date: Wed, 13 Sep 2017 13:28:39 -0400 [thread overview]
Message-ID: <20170913172839.GA12710@holos.localdomain> (raw)
In-Reply-To: <87r2vawmu6.fsf@web.de>
On 13/09/17 at 07:05pm, Michael Heerdegen wrote:
> Mark Oteiza <mvoteiza@udel.edu> writes:
>
> > Ok, great. All tests passed, so I installed it. Closing!
>
> Thanks, good work.
>
> One more small thing I thought about after Stefan's question: We have
> this sentence in the doc of `if-let*':
>
> | An element can additionally be of the form (VALUEFORM), which is
> | evaluated and checked for nil.
>
> Would it ease understanding if we would add something like "i.e. you can
> omit the SYMBOL if you are only interested in the test result".
I think so.
> Oh, and I find we have some inconsistency: I haven't looked how the
> behavior was before, but I see that `if-let*' (and thus `when-let*')
> treats an empty VARLIST as failure (the ELSEs are executed). Contrary
> to `and-let*', which treats it as success. IMO, `and-let*' does what is
> expected, and we should change `if-let*' to behave accordingly (and as
> the documentation suggests).
>
> WDYT?
Agreed. Pushed a change for both points.
next prev parent reply other threads:[~2017-09-13 17:28 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
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 [this message]
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=20170913172839.GA12710@holos.localdomain \
--to=mvoteiza@udel.edu \
--cc=28254-done@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--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).