Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113830
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
In-Reply-To: <CAJW__o1gpa5MNLB56cUvE+6HriF9YGRW3EkjWVB=Wo3g-=aBLQ@mail.gmail.com>
Date: Sun, 28 Mar 2021 09:36:30 -0400
Cc: PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <48ACB47A-76FB-414A-BEA4-9C224F005D13@newclarity.net>
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>
 <CAJW__o0WbWiofq5U0Ca-dhqH9R6bEy5O2HK5LBRFEZvt4QpYHA@mail.gmail.com>
 <CADK1yXJPK8TkGSUBnP73EOucgAO0APmuz2woUpBuN-Rdp1EXSw@mail.gmail.com>
 <CAJW__o1gpa5MNLB56cUvE+6HriF9YGRW3EkjWVB=Wo3g-=aBLQ@mail.gmail.com>
To: Kalle Sommer Nielsen <kalle@php.net>
Subject: Re: [PHP-DEV] [RFC] Auto-capture multi-line closures and
 shortfunctions take 2
From: mike@newclarity.net (Mike Schinkel)



> On Mar 28, 2021, at 8:04 AM, Kalle Sommer Nielsen <kalle@php.net> =
wrote:
>=20
> Den s=C3=B8n. 28. mar. 2021 kl. 14.30 skrev Deleu =
<deleugyn@gmail.com>:
>>=20
>> The fact that short closure is inconsistent with the rest of PHP is a =
done deal since the voting passed prior to 7.4 release. Unless there's a =
follow-up to deprecate the 7.4 short closure auto capture without `auto` =
keyword and make it look like PHP can't make up it's mind, I feel that =
your perspective doesn't match the proposed RFC. The RFC is extending =
short closure to support multiple statements and defining good semantics =
on how developers will interpret fn, =3D> and {} throughout the =
language.
>=20
> I think we have some sort of conundrum. I am not saying auto capture
> is not good semantics if that is what you are implying, I more than
> anyone would like consistency in the language but it is not a good
> language design to have two very similar features separated by a
> shorter keyword which implies totally different semantics. I don't
> find this a very intuitive way nor a good developer experience. I can
> understand that the connection of the `fn` keyword already having the
> meaning it has, but then we can bring up the side running RFC from
> Larry which proposes to make the same short syntax available for other
> function declarations, how would this work then with this mindset of
> `fn` meaning auto capture? Does that mean a procedural function
> declared with `fn` will now inherit the scope from which it was
> declared (usually the global scope)? What about methods declarations,
> do they import properties into the local scope? How does traits
> interact here, same as methods?
>=20
> This is why I think having the `fn` being an alias of `function`
> neutralizes the argument of what happens for exactly those reasonings
> above, this allows arrow functions to continue being auto capture
> without any keyword.


I am curious how requiring developers to learn that "=3D>" means =
auto-capture and having developers question when they should choose "fn" =
instead of "function" when the answer is "it does not matter" is a more =
intuitive and a better developer experience than requiring developers to =
simply learn that "fn" means auto-capture?

-Mike