Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119715
Feedback-ID: i8414410d:Fastmail
User-Agent: Cyrus-JMAP/3.9.0-alpha0-221-gec32977366-fm-20230306.001-gec329773
Mime-Version: 1.0
Message-ID: <4bf1706b-308c-4aa2-9f1d-a31add575f9c@app.fastmail.com>
In-Reply-To: 
 <CAAwdEzBP9EgA8xSYB4XXF3coetTX9uaZdVckLP5dyDuurMKRig@mail.gmail.com>
References: <8a9a04b3-45e6-47dd-dee8-0f524e49bd37@gmail.com>
 <f0b6ce61-9a9f-4598-aa97-df6ceef6be28@app.fastmail.com>
 <d1666f4b-7417-4cae-9aa0-2296a1462afb@gmail.com>
 <CAAwdEzBP9EgA8xSYB4XXF3coetTX9uaZdVckLP5dyDuurMKRig@mail.gmail.com>
Date: Wed, 15 Mar 2023 13:16:32 -0500
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Brainstorming idea: inline syntax for lexical (captured)
 variables
From: larry@garfieldtech.com ("Larry Garfield")

On Tue, Mar 14, 2023, at 10:28 PM, Alexandru P=C4=83tr=C4=83nescu wrote:
> On Wed, Mar 15, 2023 at 1:09=E2=80=AFAM Rowan Tommins <rowan.collins@g=
mail.com>
> wrote:
>
>> On 14/03/2023 22:54, Larry Garfield wrote:
>>
>> Well, a large part of my resistance to automatic capture is that it
>> makes variable scope less visible at a glance. This avoids that by st=
ill
>> having a marker for "I am from another scope", but a much less verbose
>> one than the current use() clause.
>>
>
> How about first implementing use() for anonymous classes first?
> Something like:
>
> function foo(int $outer) {
>      return new class() use($outer) {
>          public function getIt() {
>              return $outer;
>          }
>      };
> }
>
> This would help with the main problem you expressed and be a less conc=
ern
> for the future.
>
> It's a different direction from what you suggested but it might be a l=
ot
> harder to pass a $^ syntax or similar.
>
> Regards,
> Alex

For the record, while the auto-capture RFC[1] didn't reach a 2/3 majorit=
y to pass, it did have a strong majority support (62%).  Given that, I t=
hink it unlikely that a "require verbose manual capture in more places" =
proposal would fair that well.

[1] https://wiki.php.net/rfc/auto-capture-closure

--Larry Garfield