Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113824
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>
 <CADK1yXKm3ztC+hyZr_UstF_wXZWFQUhGGDScO0rhUj=pedRTLA@mail.gmail.com>
In-Reply-To: <CADK1yXKm3ztC+hyZr_UstF_wXZWFQUhGGDScO0rhUj=pedRTLA@mail.gmail.com>
Date: Sun, 28 Mar 2021 13:20:54 +0300
Message-ID: <CAJW__o0WbWiofq5U0Ca-dhqH9R6bEy5O2HK5LBRFEZvt4QpYHA@mail.gmail.com>
To: Deleu <deleugyn@gmail.com>
Cc: Rowan Tommins <rowan.collins@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Auto-capture multi-line closures and
 shortfunctions take 2
From: kalle@php.net (Kalle Sommer Nielsen)

Den s=C3=B8n. 28. mar. 2021 kl. 13.02 skrev Deleu <deleugyn@gmail.com>:
>
> This would lead to inconsistent behavior in the language when short closu=
res auto capture without the auto keyword while multi statements closure do=
esn't.
> One of the best features of these RFC are their cognitive definition that=
 is clear, concise, consistent and simple.

(First off, please read our mailing lists rules[1] and do not top post)

If we go by the inconsistent behavior then by that definition short
arrow functions are inconsistent with the rest of PHP as there is no
auto capture elsewhere.

This is not short arrow functions being expanded to support multi
lines, but rather the other way around, with multi line closures being
able to support auto capture which is identified by the `fn` keyword
and because of that, I would much rather have a `fn` be an alias of
`function` and then having the ability to put a keyword to declare
that you wish to use auto capture (which is consistent with the
exisiting design of PHP where you have to declare globals with the
`global` keyword or explicit imports to closures with the `use`
statement (which used to be done by the `lexical` keyword similarily
to the `global` keyword in early PHP 5.3.0 development) -- if you are
interested in this philosophy you can try lookup videos from some of
Rasmus' presentations where he explains his dislike with globals
coming from C). To back this up further, we also have the `static`
keyword which acts as a feature flag so it is not unnatural, the
naming of the keyword `auto` sure, but that is another discussion.

[1] https://git.php.net/?p=3Dphp-src.git;a=3Dblob_plain;f=3Ddocs/mailinglis=
t-rules.md;hb=3DHEAD

regards,

Kalle Sommer Nielsen
kalle@php.net