From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 28254@debbugs.gnu.org
Subject: bug#28254: 26.0.50; SRFI-2 and-let*
Date: Sat, 2 Sep 2017 14:41:03 -0400 [thread overview]
Message-ID: <CAM-tV-8w7YaUKcjcEC5OYB=5OE7Jx8hYkT1LxSoKX704Q99_Qw@mail.gmail.com> (raw)
In-Reply-To: <20170902133604.GA27251@holos.localdomain>
On Sat, Sep 2, 2017 at 9:36 AM, Mark Oteiza <mvoteiza@udel.edu> wrote:
> On 02/09/17 at 07:25am, Michael Heerdegen wrote:
>>
>> Isn't there a problem with EXPR being a symbol S, which already has a
>> different meaning (bind S to nil)? Though, this seems barely useful to
>> me. Anyway, introducing (EXPR) would thus be backward incompatible.
What would be the point of binding S to nil? In the foo-let macros
that would be equivalent to just putting nil (if non-list EXPRs are
supported), no?
> This single tuple special case is troublesome IMO:
>
> (if-let* (x) "dogs" "cats") => "cats"
> (if-let* (x (y 2)) "dogs" "cats") => (void-function y)
> (if-let* (x (y 1) (z 2)) "dogs" "cats") => "cats"
>
> I'm curious if this was brought up in the old discussion when this was
> implemented.
I think I'd be okay with dropping support for the S = (S nil) thing in
foo-let macros, so that all of the above would give (void-variable x).
Although perhaps the incompatibility with plain let would be annoying?
To be honest I hardly ever make use of S = (S nil) in plain let either
so it wouldn't hit me at all.
next prev parent reply other threads:[~2017-09-02 18:41 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM-tV-8w7YaUKcjcEC5OYB=5OE7Jx8hYkT1LxSoKX704Q99_Qw@mail.gmail.com' \
--to=npostavs@users.sourceforge.net \
--cc=28254@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=mvoteiza@udel.edu \
/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.