GNU bug report logs - #28254
26.0.50; SRFI-2 and-let*

Previous Next

Package: emacs;

Reported by: Mark Oteiza <mvoteiza <at> udel.edu>

Date: Sun, 27 Aug 2017 20:12:02 UTC

Severity: wishlist

Found in version 26.0.50

Done: Mark Oteiza <mvoteiza <at> udel.edu>

Bug is archived. No further changes may be made.

Full log


Message #38 received at 28254 <at> debbugs.gnu.org (full text, mbox):

From: Mark Oteiza <mvoteiza <at> udel.edu>
To: Noam Postavsky <npostavs <at> users.sourceforge.net>
Cc: Michael Heerdegen <michael_heerdegen <at> web.de>, 28254 <at> debbugs.gnu.org
Subject: Re: bug#28254: 26.0.50; SRFI-2 and-let*
Date: Sun, 3 Sep 2017 21:13:56 -0400
On 02/09/17 at 02:41pm, Noam Postavsky wrote:
>On Sat, Sep 2, 2017 at 9:36 AM, Mark Oteiza <mvoteiza <at> udel.edu> wrote:
>> 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.

FWIW, this was brought up in the original thread.
https://lists.gnu.org/archive/html/emacs-devel/2014-08/msg00228.html

IMO the original suggestion of having if-let and when-let be exclusively
single binding, while the starred versions excluding the single binding
special case would be more sane.

P.S. I just realized I didn't copy the tuple part of if-let* into
and-let* in the patch I just sent, and therefore missed the problem this
special case causes in tests.




This bug report was last modified 7 years and 253 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.