Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113823
MIME-Version: 1.0
References: <88c9eb5f-f80c-4869-b7f8-1b58b9e2eaa3@www.fastmail.com>
 <605bae82.1c69fb81.f49f7.d11eSMTPIN_ADDED_MISSING@mx.google.com>
 <919e30e7-3e5e-d955-7bb4-1e1b5825cdd1@gmail.com> <635DD146-FC6F-4991-8D2C-5A6B492722D5@newclarity.net>
 <734f12de-da98-6b76-c2fe-8682f4d177aa@gmail.com> <CALZWoqXZF9wegVGwGMjjVEV89zTjb-TYS87MqP36fSk-qJqD4g@mail.gmail.com>
 <daffe9ec-3163-25cc-bb52-587fbd2230bb@gmail.com> <36E45DD6-E2BD-4801-BAAE-4355C83D1AC3@newclarity.net>
 <CAJpLVh0ihALcqdGOCeKQ7DDXTHqOvoSW1K2SDO=VEtaJUab7zA@mail.gmail.com>
 <15AE4315-A456-4ED8-990A-49EBD76C5B46@newclarity.net> <CAJpLVh0PTjXY3ov2-XppYBR3Z4eskhMQx9xUB7egVwy0nRiFpw@mail.gmail.com>
 <BD2A7A81-C3F7-4738-8237-25B6FB776C3F@newclarity.net> <CAJpLVh25PkPEomTjfXJpdGxRx6MhQBLL0JnHajJkaniOTSDtFQ@mail.gmail.com>
 <5501FE70-FBED-47EB-8010-173644BC064F@newclarity.net> <CAJpLVh1s6bhLx_S2XBQQDe6CYf+JCM2gOQ2Wgsf3UCcU9-KCnQ@mail.gmail.com>
 <CALZWoqU5jCbC+RBZ7gxMWFDo1Qr8Es2gu=x0Sz06wL1E6NgP-Q@mail.gmail.com>
 <3d453ce7-db16-fb75-91b4-9a2a71994164@gmail.com> <CAJW__o2o5Yo5rbSfMLq5Kp45oNfQiMBThpRTJmBUkQHToVZf_g@mail.gmail.com>
In-Reply-To: <CAJW__o2o5Yo5rbSfMLq5Kp45oNfQiMBThpRTJmBUkQHToVZf_g@mail.gmail.com>
Date: Sun, 28 Mar 2021 12:02:06 +0200
Message-ID: <CADK1yXKm3ztC+hyZr_UstF_wXZWFQUhGGDScO0rhUj=pedRTLA@mail.gmail.com>
To: Kalle Sommer Nielsen <kalle@php.net>
Cc: Rowan Tommins <rowan.collins@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000042a1e305be95dcdc"
Subject: Re: [PHP-DEV] [RFC] Auto-capture multi-line closures and
 shortfunctions take 2
From: deleugyn@gmail.com (Deleu)

--00000000000042a1e305be95dcdc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

This would lead to inconsistent behavior in the language when short
closures auto capture without the auto keyword while multi statements
closure doesn't.
One of the best features of these RFC are their cognitive definition that
is clear, concise, consistent and simple.

On Sun, Mar 28, 2021, 11:26 Kalle Sommer Nielsen <kalle@php.net> wrote:

> Hi Rowan
>
> Den l=C3=B8r. 27. mar. 2021 kl. 18.05 skrev Rowan Tommins <
> rowan.collins@gmail.com>:
> > Based on those, there seems to be no way to prevent a variable being
> > captured, even if its value is immediately discarded each time the
> > closure runs. This may be less than ideal:
> >
> > $results =3D getLargeReportFromDatabase();
> > // ...
> > $fn =3D fn() {
> >      $results =3D []; // coincidentally the same name, immediately
> > assigned its own value
> >      // ...
> > }
> > unset($results); // does not free the array, because $fn has captured
> > the value
>
> I too am very concerned about this exact senario because it very
> easily overlooked. While I understand the appeal of having very short
> closures, I do think that such behavior needs to be explicit and would
> much rather prefer something like this:
>
>  - Make the `fn` keyword an alias of the `function` keyword
>  - Add a new `auto` (or similar)  keyword for explicit auto capture
>
> Something like this:
> ```php
> return function () use ($v1, $v2, $v3, $v4) {
>     /* ... */
> };
> ```
>
> Would then be abled to be turned into:
> ```php
> return auto fn () {
>     /* ... */
> };
> ```
>
> That way it is very clear that the closure is intending on auto
> capturing at this point, at the same time it also allows people like
> me who prefers the `function` keyword to write.
>
> I personally don't think adding those 5 extra characters here for
> explicitity is bad, I would like explicitly over implicitit, I can see
> how many would simply just write `fn` without knowing there is a very
> vitual difference (similar to `static` closures is rare if you don't
> intend on binding `$this`).
>
> --
> regards,
>
> Kalle Sommer Nielsen
> kalle@php.net
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
>

--00000000000042a1e305be95dcdc--