Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112261
MIME-Version: 1.0
References: <CA+kxMuRjJ5B_ykNXeMZhAd6iduh-VEk7CNP0vNuZp9fjka5_HQ@mail.gmail.com>
 <CAAKU0u=cHBO1r=vA9_KdXzrPGzQuiCksPTPYZZB5d0mSfrDxfw@mail.gmail.com>
 <CAJmy8YF2Un=Di_xOL=dnQ8nhOHO4ZbyptXz4PRLnYY=zZDzK1A@mail.gmail.com>
 <CA+kxMuTm+UorKQ=YU96c_k6H-c3CVhmA7gu12K-6Sf532Qrpag@mail.gmail.com>
 <55e200cf-ed16-e935-4e09-728ce3362cba@gmx.de> <CAEsg9X2w=Bty-4oVsN1ac6+J6PFko7XAajGfk4os7cruQS8Yxw@mail.gmail.com>
In-Reply-To: <CAEsg9X2w=Bty-4oVsN1ac6+J6PFko7XAajGfk4os7cruQS8Yxw@mail.gmail.com>
Date: Fri, 20 Nov 2020 09:14:41 -0600
Message-ID: <CAESVnVp42zB6paMoBfKAfDF8kdH3_3-8KZkvk=AzPESmH57C9Q@mail.gmail.com>
To: David Rodrigues <david.proweb@gmail.com>
Cc: "Christoph M. Becker" <cmbecker69@gmx.de>, Dan Ackroyd <Danack@basereality.com>, 
	Hans Henrik Bergan <divinity76@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000006b205405b48b4e84"
Subject: Re: [PHP-DEV] [RFC] Draft - Closure self reference
From: pollita@php.net (Sara Golemon)

--0000000000006b205405b48b4e84
Content-Type: text/plain; charset="UTF-8"

On Wed, Nov 11, 2020 at 12:37 PM David Rodrigues <david.proweb@gmail.com>
wrote:

> My suggestion is to reuse the keyword `as` to set a variable that will
> represent its own closure. It is more flexible once that we could choose
> any name and reuse in nested closures. It is pretty similar to how SQL
> works too.
>
> function fn1() as $lambda1 {
>     return function() as $lambda2 use ($lambda1) {
>         return [ gettype($lambda1), gettype($lambda2) ];
>     };
> }
>
>
My initial reaction to this is:  Technically doable (easy even), but looks
a bit... ugly? weird? surprising?

I think my main objection to it is how much is now stacked after the
parameter list:

function($args...) : returnType as $local use ($captures...) {
  ...
};

That's a lot of... stuff (granted, we have most of it already) and how it
looks when stacked together gets funky.

Is it `returnType as $thing` ?  That doesn't read well, but I don't see us
making return type movable.  as/use should be placable in either order, but
maybe we give them required order anyway?

TLDR; Long winded way to say I'm not inherently against this, and I like
the idea of a lambda being able to recurse (not that I can ever recall
having use for it, but maybe I fell back on named functions for that), I
just think it's getting a bit wordy.

-Sara

--0000000000006b205405b48b4e84--