Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113829
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>
 <CAJW__o0WbWiofq5U0Ca-dhqH9R6bEy5O2HK5LBRFEZvt4QpYHA@mail.gmail.com>
 <CADK1yXJPK8TkGSUBnP73EOucgAO0APmuz2woUpBuN-Rdp1EXSw@mail.gmail.com> <CAJW__o1gpa5MNLB56cUvE+6HriF9YGRW3EkjWVB=Wo3g-=aBLQ@mail.gmail.com>
In-Reply-To: <CAJW__o1gpa5MNLB56cUvE+6HriF9YGRW3EkjWVB=Wo3g-=aBLQ@mail.gmail.com>
Date: Sun, 28 Mar 2021 14:34:59 +0200
Message-ID: <CADK1yXJyUbm8SZFENOr6x62CB2tpb_qYLuZZzBS5g17y+SYtyQ@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="00000000000061f8b605be9800e4"
Subject: Re: [PHP-DEV] [RFC] Auto-capture multi-line closures and
 shortfunctions take 2
From: deleugyn@gmail.com (Deleu)

--00000000000061f8b605be9800e4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

>
> 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?
>

I think I remember the 1st version of Larry's RFC proposing `public fn
classMethod(): bool =3D> $this->myAttr;` as a class method which seems to
match what you're trying to say here, but that has been withdrawn and the
RFC no longer proposes the fn keyword for class methods or function
declarations, which is discussed under *Background* of RFC
https://wiki.php.net/rfc/auto-capture-closure. Larry and Nuno may correct
me if I'm wrong but as far as I understood, that change happened to address
exactly the points you're describing here: what does `public fn
classMethod(): bool` would capture? There's actually little to no reason to
do it. Larry's RFC still proposes a great improvement for
getters/setters/short methods and Nuno's RFC allows us to write code that
is naturally expected to work, such as `fn () =3D> {...}`.

As for making `fn` an alias of `function` I believe that is already broken
because of 7.4 arrow functions. As you describe, that would be "an
exception" to PHP syntax, but more pressing it means that we would be
wasting the potential of 2 separate keywords having different goals. I
think it was Nikita that once said that we have a very limited budget on
what we can do/offer through programming syntax and throwing `fn` out would
be such a waste of that limited budget.

--=20
Marco Aur=C3=A9lio Deleu

--00000000000061f8b605be9800e4--