Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117891
MIME-Version: 1.0
References: <2b35605f-8da8-46b1-aec3-00bd1bfe47fd@www.fastmail.com>
In-Reply-To: <2b35605f-8da8-46b1-aec3-00bd1bfe47fd@www.fastmail.com>
Date: Thu, 9 Jun 2022 20:36:23 +0200
Message-ID: <CABdc3WrGPEGi_iS0=QbL3H5LxEJ-SSFKwHzrcyLk6kWA2tF9uQ@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000f1c80105e1081919"
Subject: Re: [PHP-DEV] [RFC] Short Closures 2, aka auto-capture take 3
From: michal.brzuchalski@gmail.com (=?UTF-8?Q?Micha=C5=82_Marcin_Brzuchalski?=)

--000000000000f1c80105e1081919
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Larry,

czw., 9 cze 2022 o 18:34 Larry Garfield <larry@garfieldtech.com> napisa=C5=
=82(a):

> Last year, Nuno Maduro and I put together an RFC for combining the
> multi-line capabilities of long-closures with the auto-capture compactnes=
s
> of short-closures.  That RFC didn't fully go to completion due to concern=
s
> over the performance impact, which Nuno and I didn't have bandwidth to
> resolve.
>
> Arnaud Le Blanc has now picked up the flag with an improved implementatio=
n
> that includes benchmarks showing an effectively net-zero performance
> impact, aka, good news as it avoids over-capturing.
>
> The RFC has therefore been overhauled accordingly and is now ready for
> consideration.
>
> https://wiki.php.net/rfc/auto-capture-closure


Nice work. Well-described behaviors.

One question, more around future scope or related functionality in the
future:
A future RFC for "short-methods" described here in one of your declined RFC
https://wiki.php.net/rfc/short-functions in the past could be revived with
no conflicts in the scope of methods?

class Foo {
    public string $firstName =3D 'John';
    public function getFirstName(): string =3D> $this->firstName;
}

I'm asking if I understand the scopes of this and previous RFCs correctly
and if they don't block in future "short-methods"?

Cheers,
Micha=C5=82 Marcin Brzuchalski

--000000000000f1c80105e1081919--