GNU logs - #30237, boring messages

Message sent to bug-guile@HIDDEN:

Subject: bug#30237: Generalizing =?UTF-8?Q?=E2=80=98and=3D>=E2=80=99?=
Resent-From: Mathieu Lirzin <mthl@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guile@HIDDEN
Resent-Date: Wed, 24 Jan 2018 12:11:01 +0000
Resent-Message-ID: <handler.30237.B.15167958361995 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 30237 <at> debbugs.gnu.org
From: Mathieu Lirzin <mthl@HIDDEN>
Date: Wed, 24 Jan 2018 13:10:20 +0100
Message-ID: <877es731ar.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Hello,

Here is a proposal for generalizing =E2=80=98and=3D>=E2=80=99 to a pipeline=
 of procedures.
It acts like a =E2=80=9Cbind=E2=80=9D operator in an ad-hoc =E2=80=9CMaybe=
=E2=80=9D monad which uses #f
to represent the absence of value.  Not sure if it is useful in
practice, but it feels like a natural generalization.

The current definition is the following:

  (define (and=3D> value procedure)
    (and value (procedure value)))

Here is my proposition:

  (define-syntax and=3D>
    (syntax-rules ()
      ((_) #t)
      ((_ val) val)
      ((_ val proc)
       (and val (proc val)))
      ((_ val proc proc* ...)
       (and=3D> (and val (proc val)) proc* ...))))

Let me know if such change is welcome or not, so I can provide a
complete patch including documentation.  Even if it's a small change, I
would like to assign copyright for future changes.

Thanks.

--=20
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Mathieu Lirzin <mthl@HIDDEN>
Subject: bug#30237: Acknowledgement (Generalizing =?UTF-8?Q?=E2=80=98and=3D>=E2=80=99?=)
Message-ID: <handler.30237.B.15167958361995.ack <at> debbugs.gnu.org>
References: <877es731ar.fsf@HIDDEN>
X-Gnu-PR-Message: ack 30237
X-Gnu-PR-Package: guile
Reply-To: 30237 <at> debbugs.gnu.org
Date: Wed, 24 Jan 2018 12:11:01 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-guile@HIDDEN

If you wish to submit further information on this problem, please
send it to 30237 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
30237: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D30237
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-guile@HIDDEN:

Subject: bug#30237: Generalizing =?UTF-8?Q?=E2=80=98and=3D>=E2=80=99?=
Resent-From: Mark H Weaver <mhw@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guile@HIDDEN
Resent-Date: Wed, 24 Jan 2018 15:03:01 +0000
Resent-Message-ID: <handler.30237.B30237.15168061432643 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Mathieu Lirzin <mthl@HIDDEN>
Cc: 30237 <at> debbugs.gnu.org
From: Mark H Weaver <mhw@HIDDEN>
References: <877es731ar.fsf@HIDDEN>
Date: Wed, 24 Jan 2018 10:01:44 -0500
In-Reply-To: <877es731ar.fsf@HIDDEN> (Mathieu Lirzin's message of "Wed, 24
 Jan 2018 13:10:20 +0100")
Message-ID: <877es7ti5j.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Hi Mathieu,

Mathieu Lirzin <mthl@HIDDEN> writes:

> Here is a proposal for generalizing =E2=80=98and=3D>=E2=80=99 to a pipeli=
ne of procedures.
> It acts like a =E2=80=9Cbind=E2=80=9D operator in an ad-hoc =E2=80=9CMayb=
e=E2=80=9D monad which uses #f
> to represent the absence of value.  Not sure if it is useful in
> practice, but it feels like a natural generalization.
>
> The current definition is the following:
>
>   (define (and=3D> value procedure)
>     (and value (procedure value)))
>
> Here is my proposition:
>
>   (define-syntax and=3D>
>     (syntax-rules ()
>       ((_) #t)
>       ((_ val) val)
>       ((_ val proc)
>        (and val (proc val)))
>       ((_ val proc proc* ...)
>        (and=3D> (and val (proc val)) proc* ...))))

Be careful, macros are different than procedures!  Instead of binding
values to variables, they bind _unevaluated_ forms to pattern variables.
So 'val' is a misleading name for the first operand of the macro above.
In fact, what's being bound there is an _expression_, and you are then
expanding this into something that contains two copies of that
expression.  So, for example:

  (and=3D> (compile-webkitgtk)
         test
         install)

expands into:

  (and=3D> (and (compile-webkitgtk)
              (test (compile-webkitgtk)))
         install)

which expands into:

  (and (and (compile-webkitgtk)
            (test (compile-webkitgtk)))
       (install (and (compile-webkitgtk)
                     (test (compile-webkitgtk)))))

So you end up compiling webkitgtk 4 times, and testing it twice, before
finally installing it.  More generally, if you pass N+1 operands, the
first operand will be evaluated 2^N times.

The other problem is that 'and=3D>' is currently a procedure, and you're
replacing it with a macro.  There are a couple of issues with this.  One
is that procedures are first-class objects in Scheme, but macros aren't.
Procedures can be passed as arguments to procedures, stored in data
structures, etc, but macros cannot.

For example, if 'and=3D>' is a procedure, you can write:

  (map and=3D> vals procs)

but you can't do this if 'and=3D>' is a macro.

The other problem with changing 'and=3D>' to a macro is that this
effectively changes the ABI of Guile, which we can't do within a stable
release series (2.2.x).  Existing .go files that use 'and=3D>' were
compiled to generate a normal procedure call for 'and=3D>', and if that
procedure no longer exists then the code will break.  This change
requires all users of 'and=3D>' to be recompiled.

> Let me know if such change is welcome or not, so I can provide a
> complete patch including documentation.

I think it's worth considering something along these lines for the
'master' branch which will eventually become Guile 3, although in order
to support existing callers that expect 'and=3D>' to be a first-class
procedure, we might want to arrange for a bare 'and=3D>' to expand into a
reference to a first-class procedure that does the same job, similar to
what we do with 'define-inlinable'.

The other option would be to implement your enhanced 'and=3D>' as a normal
procedure using case-lambda, maybe something like this:

  (define and=3D>
    (case-lambda
      ((val proc) (and val (proc val)))
      ((val . procs)
       (let loop ((val val) (procs procs))
         (if (null? procs)
             val
             (and val (loop ((car procs) val)
                            (cdr procs))))))
      (() #t)))

The first case is not strictly needed, but is included as an
optimization to avoid heap-allocating a list for the 'procs' rest
argument in the common case of two arguments.

The second case is implemented as a loop instead of a recursive call to
'and=3D>', to prevent repeatedly heap-allocating the rest list on each
iteration, which would lead to O(N^2) allocations for N arguments.  It
would be nicer to use 'match' here, but since 'and=3D>' is defined early
in boot-9.scm, we must restrict ourselves to core functionality in its
implementation.

I'm not sure if it makes sense to include the final (nullary) case.
Unlike 'and', 'or', '+', '*' and similar operations where every argument
is treated uniformally, in this case the first argument is qualitatively
different than the others.  Therefore, it seems to me that this
procedure naturally generalizes down to 1 argument, but no further.

Finally, there still some question in my mind whether this
generalization would be useful in practice.  Have you found a real-world
use case where this generalized 'and=3D>' makes life easier?

Do you know about SRFI-2 (and-let*)?  How would that work for your use
case?

     Regards,
       Mark

Message sent to bug-guile@HIDDEN:

Subject: bug#30237: Generalizing =?UTF-8?Q?=E2=80=98and=3D>=E2=80=99?=
Resent-From: Mathieu Lirzin <mthl@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guile@HIDDEN
Resent-Date: Wed, 24 Jan 2018 20:09:01 +0000
Resent-Message-ID: <handler.30237.B30237.15168245194385 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Mark H Weaver <mhw@HIDDEN>
Cc: 30237 <at> debbugs.gnu.org
From: Mathieu Lirzin <mthl@HIDDEN>
References: <877es731ar.fsf@HIDDEN> <877es7ti5j.fsf@HIDDEN>
Date: Wed, 24 Jan 2018 21:08:25 +0100
In-Reply-To: <877es7ti5j.fsf@HIDDEN> (Mark H. Weaver's message of "Wed, 24
 Jan 2018 10:01:44 -0500")
Message-ID: <87y3kn10li.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Hello Mark,

Mark H Weaver <mhw@HIDDEN> writes:

> Mathieu Lirzin <mthl@HIDDEN> writes:
>
>> Here is a proposal for generalizing =E2=80=98and=3D>=E2=80=99 to a pipel=
ine of procedures.
>> It acts like a =E2=80=9Cbind=E2=80=9D operator in an ad-hoc =E2=80=9CMay=
be=E2=80=9D monad which uses #f
>> to represent the absence of value.  Not sure if it is useful in
>> practice, but it feels like a natural generalization.
>>
>> The current definition is the following:
>>
>>   (define (and=3D> value procedure)
>>     (and value (procedure value)))
>>
>> Here is my proposition:
>>
>>   (define-syntax and=3D>
>>     (syntax-rules ()
>>       ((_) #t)
>>       ((_ val) val)
>>       ((_ val proc)
>>        (and val (proc val)))
>>       ((_ val proc proc* ...)
>>        (and=3D> (and val (proc val)) proc* ...))))
>
> Be careful, macros are different than procedures!  Instead of binding
> values to variables, they bind _unevaluated_ forms to pattern variables.
> So 'val' is a misleading name for the first operand of the macro above.
> In fact, what's being bound there is an _expression_, and you are then
> expanding this into something that contains two copies of that
> expression.  So, for example:
>
>   (and=3D> (compile-webkitgtk)
>          test
>          install)
>
> expands into:
>
>   (and=3D> (and (compile-webkitgtk)
>               (test (compile-webkitgtk)))
>          install)
>
> which expands into:
>
>   (and (and (compile-webkitgtk)
>             (test (compile-webkitgtk)))
>        (install (and (compile-webkitgtk)
>                      (test (compile-webkitgtk)))))
>
> So you end up compiling webkitgtk 4 times, and testing it twice, before
> finally installing it.  More generally, if you pass N+1 operands, the
> first operand will be evaluated 2^N times.

Indeed I overlooked that.

> The other problem is that 'and=3D>' is currently a procedure, and you're
> replacing it with a macro.  There are a couple of issues with this.  One
> is that procedures are first-class objects in Scheme, but macros aren't.
> Procedures can be passed as arguments to procedures, stored in data
> structures, etc, but macros cannot.
>
> For example, if 'and=3D>' is a procedure, you can write:
>
>   (map and=3D> vals procs)
>
> but you can't do this if 'and=3D>' is a macro.
>
> The other problem with changing 'and=3D>' to a macro is that this
> effectively changes the ABI of Guile, which we can't do within a stable
> release series (2.2.x).  Existing .go files that use 'and=3D>' were
> compiled to generate a normal procedure call for 'and=3D>', and if that
> procedure no longer exists then the code will break.  This change
> requires all users of 'and=3D>' to be recompiled.

I initially implemented it as a procedure but move to the macro side of
thing in an attempt to generate more efficient code while handling
procedures that return multiple values.  But this can't work given the
issue you described above.

>> Let me know if such change is welcome or not, so I can provide a
>> complete patch including documentation.
>
> I think it's worth considering something along these lines for the
> 'master' branch which will eventually become Guile 3, although in order
> to support existing callers that expect 'and=3D>' to be a first-class
> procedure, we might want to arrange for a bare 'and=3D>' to expand into a
> reference to a first-class procedure that does the same job, similar to
> what we do with 'define-inlinable'.

I don't think making it a macro worths the breaking change.

> The other option would be to implement your enhanced 'and=3D>' as a normal
> procedure using case-lambda, maybe something like this:
>
>   (define and=3D>
>     (case-lambda
>       ((val proc) (and val (proc val)))
>       ((val . procs)
>        (let loop ((val val) (procs procs))
>          (if (null? procs)
>              val
>              (and val (loop ((car procs) val)
>                             (cdr procs))))))
>       (() #t)))
>
> The first case is not strictly needed, but is included as an
> optimization to avoid heap-allocating a list for the 'procs' rest
> argument in the common case of two arguments.
>
> The second case is implemented as a loop instead of a recursive call to
> 'and=3D>', to prevent repeatedly heap-allocating the rest list on each
> iteration, which would lead to O(N^2) allocations for N arguments.  It
> would be nicer to use 'match' here, but since 'and=3D>' is defined early
> in boot-9.scm, we must restrict ourselves to core functionality in its
> implementation.

That's a clear explanation.  IMO It would be nice if multiple values
were handled too.  here is one solution inspired by =E2=80=98compose=E2=80=
=99.

(define and=3D>
  (case-lambda
    ((val proc) (and val (proc val)))
    ((val proc . procs)
     (let loop ((p proc) (ps procs))
       (if (null? ps)
	   (p val)
	   (loop (lambda args
		   (call-with-values (lambda () (apply p args))
		     (lambda (arg0 . args*)
		       (and arg0 (apply (car ps) arg0 args*)))))
		 (cdr ps)))))))

I am not sure if there is a way to avoid constructing the composition of
functions.

> I'm not sure if it makes sense to include the final (nullary) case.
> Unlike 'and', 'or', '+', '*' and similar operations where every argument
> is treated uniformally, in this case the first argument is qualitatively
> different than the others.  Therefore, it seems to me that this
> procedure naturally generalizes down to 1 argument, but no further.

I don't think so, I defined it only because I took inspiration from
=E2=80=98and=E2=80=99.

> Finally, there still some question in my mind whether this
> generalization would be useful in practice.  Have you found a real-world
> use case where this generalized 'and=3D>' makes life easier?

Not really.  :-)

> Do you know about SRFI-2 (and-let*)?  How would that work for your use
> case?

Yes I know about =E2=80=98and-let*=E2=80=99 which is a proper way to do pip=
elining while
checking for #f.  My motivation for extending =E2=80=98and=3D>=E2=80=99 was=
 to have
something similar but without the special syntax.

Thanks for the in-depth review.

--=20
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

Message sent to bug-guile@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#30237: Generalizing =?UTF-8?Q?=E2=80=98and=3D>=E2=80=99?=
Resent-From: Mark H Weaver <mhw@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guile@HIDDEN
Resent-Date: Wed, 31 Jan 2018 04:33:02 +0000
Resent-Message-ID: <handler.30237.B30237.151737315726525 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 30237
X-GNU-PR-Package: guile
X-GNU-PR-Keywords: 
To: Mathieu Lirzin <mthl@HIDDEN>
Cc: 30237 <at> debbugs.gnu.org
Received: via spool by 30237-submit <at> debbugs.gnu.org id=B30237.151737315726525
          (code B ref 30237); Wed, 31 Jan 2018 04:33:02 +0000
Received: (at 30237) by debbugs.gnu.org; 31 Jan 2018 04:32:37 +0000
Received: from localhost ([127.0.0.1]:50176 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1egk4b-0006tk-2r
	for submit <at> debbugs.gnu.org; Tue, 30 Jan 2018 23:32:37 -0500
Received: from world.peace.net ([50.252.239.5]:51314)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <mhw@HIDDEN>) id 1egk4Z-0006tS-H0
 for 30237 <at> debbugs.gnu.org; Tue, 30 Jan 2018 23:32:35 -0500
Received: from pool-72-93-27-251.bstnma.east.verizon.net ([72.93.27.251]
 helo=jojen)
 by world.peace.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.89) (envelope-from <mhw@HIDDEN>)
 id 1egk4T-0001us-E1; Tue, 30 Jan 2018 23:32:29 -0500
From: Mark H Weaver <mhw@HIDDEN>
References: <877es731ar.fsf@HIDDEN> <877es7ti5j.fsf@HIDDEN>
 <87y3kn10li.fsf@HIDDEN>
Date: Tue, 30 Jan 2018 23:31:52 -0500
In-Reply-To: <87y3kn10li.fsf@HIDDEN> (Mathieu Lirzin's message of "Wed, 24
 Jan 2018 21:08:25 +0100")
Message-ID: <87shamvebr.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: 0.0 (/)

Mathieu Lirzin <mthl@HIDDEN> writes:

> IMO It would be nice if multiple values
> were handled too.  here is one solution inspired by =E2=80=98compose=E2=
=80=99.
>
> (define and=3D>
>   (case-lambda
>     ((val proc) (and val (proc val)))
>     ((val proc . procs)
>      (let loop ((p proc) (ps procs))
>        (if (null? ps)
> 	   (p val)
> 	   (loop (lambda args
> 		   (call-with-values (lambda () (apply p args))
> 		     (lambda (arg0 . args*)
> 		       (and arg0 (apply (car ps) arg0 args*)))))
> 		 (cdr ps)))))))

This generalization will inevitably slow it down, and it's not clear
that this is useful in practice.  It's also not particularly natural,
because these return value(s) somehow need to be interpreted as a
boolean.  There are multiple ways to do that, and it's not clear which
is the best way.

I think we should resist the temptation to make simple things more
complicated without good reason.  Making things more complicated always
has a cost.  I'm a big believer in keeping things simple, especially the
widely used primitive operations.

Thoughts?

      Mark

Message sent to bug-guile@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#30237: Generalizing =?UTF-8?Q?=E2=80=98and=3D>=E2=80=99?=
Resent-From: Mathieu Lirzin <mthl@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guile@HIDDEN
Resent-Date: Wed, 31 Jan 2018 14:24:03 +0000
Resent-Message-ID: <handler.30237.B30237.151740863614380 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 30237
X-GNU-PR-Package: guile
X-GNU-PR-Keywords: 
To: Mark H Weaver <mhw@HIDDEN>
Cc: 30237 <at> debbugs.gnu.org
Received: via spool by 30237-submit <at> debbugs.gnu.org id=B30237.151740863614380
          (code B ref 30237); Wed, 31 Jan 2018 14:24:03 +0000
Received: (at 30237) by debbugs.gnu.org; 31 Jan 2018 14:23:56 +0000
Received: from localhost ([127.0.0.1]:50433 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1egtIp-0003js-TQ
	for submit <at> debbugs.gnu.org; Wed, 31 Jan 2018 09:23:56 -0500
Received: from eggs.gnu.org ([208.118.235.92]:53897)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <mthl@HIDDEN>) id 1egtIn-0003jY-Bi
 for 30237 <at> debbugs.gnu.org; Wed, 31 Jan 2018 09:23:54 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <mthl@HIDDEN>) id 1egtIg-0003cc-U6
 for 30237 <at> debbugs.gnu.org; Wed, 31 Jan 2018 09:23:48 -0500
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,T_RP_MATCHES_RCVD
 autolearn=disabled version=3.3.2
Received: from fencepost.gnu.org ([2001:4830:134:3::e]:53017)
 by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <mthl@HIDDEN>)
 id 1egtIg-0003cW-QP; Wed, 31 Jan 2018 09:23:46 -0500
Received: from [2a01:e35:2ec2:e580:7d5f:f616:fc6f:3970] (port=39932 helo=godel)
 by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.82) (envelope-from <mthl@HIDDEN>)
 id 1egtIg-0006Uz-3Z; Wed, 31 Jan 2018 09:23:46 -0500
From: Mathieu Lirzin <mthl@HIDDEN>
References: <877es731ar.fsf@HIDDEN> <877es7ti5j.fsf@HIDDEN>
 <87y3kn10li.fsf@HIDDEN> <87shamvebr.fsf@HIDDEN>
Date: Wed, 31 Jan 2018 15:23:43 +0100
In-Reply-To: <87shamvebr.fsf@HIDDEN> (Mark H. Weaver's message of "Tue, 30
 Jan 2018 23:31:52 -0500")
Message-ID: <87shamm7io.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 2001:4830:134:3::e
X-Spam-Score: -5.0 (-----)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -5.0 (-----)

Mark H Weaver <mhw@HIDDEN> writes:

> This generalization will inevitably slow it down, and it's not clear
> that this is useful in practice.  It's also not particularly natural,
> because these return value(s) somehow need to be interpreted as a
> boolean.  There are multiple ways to do that, and it's not clear which
> is the best way.
>
> I think we should resist the temptation to make simple things more
> complicated without good reason.  Making things more complicated always
> has a cost.  I'm a big believer in keeping things simple, especially the
> widely used primitive operations.

Generalizing the arity of things tends to make them more =E2=80=9Csimple=E2=
=80=9D for
example thinking of =E2=80=98+=E2=80=99 as an arbitrary arity function inst=
ead of a
binary operator is simpler.

I am realizing that In this case, the semantics are indeed unclear for
multiple values.  For example if multiple values were to be handled then
=E2=80=98(and=3D> (values 1 2) list)=E2=80=99 should work in the first plac=
e.  Moreover as
you pointed what should be done regarding the truthiness of multiple
values is not clear either.  As a consequence I withdraw my proposition
to generalize =E2=80=98and=3D>=E2=80=99 to multiple values.

Having said that I think the implementation you previously proposed
(without the arity 0 case) keep things simple:

  (define and=3D>
    (case-lambda
      ((val proc) (and val (proc val)))
      ((val . procs)
       (let loop ((val val) (procs procs))
         (if (null? procs)
             val
             (and val (loop ((car procs) val)
                            (cdr procs))))))))

> Finally, there still some question in my mind whether this
> generalization would be useful in practice.  Have you found a
> real-world use case where this generalized 'and=3D>' makes life easier?

I took some time to think about a pseudo-realistic use case.  Consider
some configuration variables that are set from the process environment.
We want to check and transform what the user provides with some slight
variations for each variable:

  ;;; Higher-order utilities.

  (define (ensure pred)
    (lambda (val)
      (and (pred val) val)))

  (define (check pred msg)
    (lambda (val)
      (unless (pred val)
        (display msg))
      val))

  ;;; Process and check variables (unrealistic but give an idea).

  (define (split-path str)
    (string-split str #\:))

  (define (no-empty-strings? lst)
    (not (any (lambda (str) (string=3D? "" str)) lst)))

  (define (keep-existing-files lst)
    (filter file-exists? lst))

  (define (warn-deprecated-path lst)
    (when (any (lambda (string-suffix? "/old-bar")))
       (display "Please don't refer to \"old-bar\" for XYZ reason")))

  ;;; Global variables.

  (define %foo
    ;; Apply procedures in a pipeline fashion...
    (and=3D> (and=3D> (and=3D> (and=3D> (getenv "FOO") split-path)
                         (ensure no-empty-strings?))
                  keep-existing-files)
           (ensure pair?)))

  (define %bar
    ;; ...or with more idiomatic procedure calls.
    (let ((lst (split-path (or (getenv "BAR")
                               "/etc/bar:/usr/share/bar"))))
      (when (no-empty-strings? lst)
        (warn-deprecated-path lst)
        lst)))

Handling arbitrary arities would allow rewriting those variables in a
more elegant way:

  (define %foo
    (and=3D> (getenv "FOO")
           split-path
           (ensure no-empty-strings?)
           keep-existing-files
           (ensure pair?)))

  (define (no-deprecated-dirs? lst)
    (not (any (lambda (str) (string-suffix? "/old-bar" str)) lst)))

  (define %bar
    (and=3D> (or (getenv "BAR") "/etc/bar:/usr/share/bar")
           split-path
           (ensure no-empty-strings?)
           (check no-deprecated-dirs?
                  "Please don't refer to \"old-bar\" for XYZ reason")))

=E2=80=98and-let*=E2=80=99 would be a reasonable alternative but the benefi=
t of this
form is that it favours the use of higher-order procedures in place of
special syntax.

WDYT?

--=20
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

Message received at control <at> debbugs.gnu.org:

Received: (at control) by debbugs.gnu.org; 18 May 2021 15:50:16 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Tue May 18 11:50:16 2021
Received: from localhost ([127.0.0.1]:56996 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1lj1z5-0005cq-Rv
	for submit <at> debbugs.gnu.org; Tue, 18 May 2021 11:50:15 -0400
Received: from mail-ej1-f43.google.com ([209.85.218.43]:38475)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <taylan.kammer@HIDDEN>) id 1lj1z3-0005cX-I3
 for control <at> debbugs.gnu.org; Tue, 18 May 2021 11:50:13 -0400
Received: by mail-ej1-f43.google.com with SMTP id b25so15360552eju.5
 for <control <at> debbugs.gnu.org>; Tue, 18 May 2021 08:50:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=to:from:subject:message-id:date:user-agent:mime-version
 :content-language:content-transfer-encoding;
 bh=8T998ivlvN11H+eaWceqnl3c92/o9nS9TCPWheC4dDs=;
 b=bxtE7VX79pkugBnwOu98YqM0V37X2Vw2n3pBycQD3VDdZj7lcIz7lg1ck8WXOPdDWP
 0IdW5NzjNVizh5zmjShUsnXM9ume0+/BkCaYs1t8f6sa3FXf2HI/lQii+1yUy6IK9XsG
 Rn6ptuXXoUvyZmPQThQRIQKRFsHg+7rWGZZQhrEH5gIrs+ceI745JOkeF6r71b86oPQs
 Fk1/HhlA43N3j4KKGQMmEai5dLo5gAzXSkKifG/NyzFbEgYz1sP3nkYm/2+nwYpwVpdB
 tnTnB5dQerEK5l2mE9hclRh4mdKaqQwsFT2wpyq0WN/GaGCIii9fbq8s1cCzPUHCNzyT
 kZKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:to:from:subject:message-id:date:user-agent
 :mime-version:content-language:content-transfer-encoding;
 bh=8T998ivlvN11H+eaWceqnl3c92/o9nS9TCPWheC4dDs=;
 b=FB2FGvIoctgwpQX1nytxERLL0e/1A4kIzuWCcEMXZmjn8TJSkw40A7QiFKyiJkM5a1
 r3Je6tA60bfvlQm7D/X7jA/Gojmnd16xD7Hl3Xi5NgqyT3hA9Lyf0XWsYqlJoKjkO+Xs
 ATk/UB0RWQOuZJj0nT2iKhus7SP1V1KnCI7NYfcUqwOTg8YYlH2eDzxOGmCbHfBjhTQA
 1FjOkccO0lPfnajG8eMytq7e/bnBzn/6++9slyO83QlEWUy02tM7ZNCUHCPB+qWvk02V
 mZCSepppArtH5RZJ+hsgFjvbYsNiSdwuIaN3/r5fBhF5gL2lQLlDdW0JXDKA2vPMsNq7
 5oSg==
X-Gm-Message-State: AOAM533655eFhn39QHH2KRe+xc0Y/VWSs6lr0demQz1eG5pgb579KFzI
 RxCGC53HWYQl9k2gGsBrB20nVquMKD/hyQ==
X-Google-Smtp-Source: ABdhPJz8E1YbQvKZqxda9d/bPN88pKvfgSiwQt6XH9TP33G85HcINeMes0VKMcaEq7CcBdA2S22hAw==
X-Received: by 2002:a17:906:1311:: with SMTP id
 w17mr6949524ejb.182.1621353007653; 
 Tue, 18 May 2021 08:50:07 -0700 (PDT)
Received: from [192.168.178.20] (b2b-109-90-125-150.unitymedia.biz.
 [109.90.125.150])
 by smtp.gmail.com with ESMTPSA id n12sm10570571edq.40.2021.05.18.08.50.07
 for <control <at> debbugs.gnu.org>
 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
 Tue, 18 May 2021 08:50:07 -0700 (PDT)
To: control <at> debbugs.gnu.org
From: Taylan Kammer <taylan.kammer@HIDDEN>
Subject: 30237 wishlist
Message-ID: <aaa2691f-af5f-dacf-8524-2c2d33ff5d9c@HIDDEN>
Date: Tue, 18 May 2021 17:50:03 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.10.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Debbugs-Envelope-To: control
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

severity 30237 wishlist

Last modified: Tue, 18 May 2021 16:00:02 UTC

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