Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112152
MIME-Version: 1.0
References: <CALZWoqU_qQQiQ5O6Pa8Upxo2FYZ2hpMA0dy9=CZndeEFsijgxA@mail.gmail.com>
 <446c9894-191f-e53b-4534-31c4e7b91d7b@gmail.com> <881e2335-5f81-0d79-6a17-06bc20f14223@gmx.net>
 <CADK1yX+0EDTuZ2Sg20_xJH02zLC15Ks1jcYR5zfECdnUBsfUFQ@mail.gmail.com>
 <873361ff-02c8-b9df-9b7a-c9e89e25a880@gmx.net> <7F014A40-2D47-4DA6-8A38-59518218F9CA@stitcher.io>
 <CAFPFaMKSVuWp9ZmdUQavE6vT=qokZpBfmrMc9=Wkot=r5fiJHA@mail.gmail.com>
 <9A58B811-37C4-46C8-A7A9-B558752362F3@stitcher.io> <CAFPFaM+aeqrvaPpAUgZHV703PGcQ=puadeAKQkctxR=P6bKcwg@mail.gmail.com>
 <CAG9XoMRnYZ_b1pLsM2qFa-r19QJx19PE1mR_p_uoQMzz3R66mA@mail.gmail.com> <9aa03cfc-a067-cc07-8dd9-50b95ae681ed@gmail.com>
In-Reply-To: <9aa03cfc-a067-cc07-8dd9-50b95ae681ed@gmail.com>
Date: Fri, 30 Oct 2020 22:44:41 +0100
Message-ID: <CAG9XoMSzANKf4bDNbad3jr44T5O9Ynh+fkm701xNVhznVxyBWA@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000007b6a4305b2ea4efa"
Subject: Re: [PHP-DEV] RFC: Support for multi-line arrow functions
From: benjamin.morel@gmail.com (Benjamin Morel)

--0000000000007b6a4305b2ea4efa
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, 30 Oct 2020 at 19:07, Rowan Tommins <rowan.collins@gmail.com> wrote=
:

> Just to be clear, the major gain here is not replacing the 10 characters
> "function()" with the 7 characters "fn() =3D>", it is eliminating the lis=
t
> of captured variables. So you would get equally clean code with a
> "capture all" syntax, such as:
>
>      return $connection->transactional(function() use(*) {
>
> or Sara's suggestion from earlier today:
>
>      return $connection->transactional(function() use($) {
>

Any of those would be a large improvement over the current situation I
agree.

That being said, for what it's worth, I've also proposed on the PR on GitHu=
b
<https://github.com/php/php-src/pull/6246#issuecomment-719074545> an
alternative syntax for a closure that takes no parameters and inherits the
full scope:

    $connection->transactional({
        // ...
    });

So yes, this would be a closure:

    $a =3D {};

I'm not sure if this would be considered (additionally, not as a
replacement), but I thought it'd be worth mentioning, as it would offer an
elegant solution for methods whose body is pretty much only a call to a
method wrapping a closure.

=E2=80=94 Benjamin

--0000000000007b6a4305b2ea4efa--