Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112005
To: internals@lists.php.net
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>
Message-ID: <873361ff-02c8-b9df-9b7a-c9e89e25a880@gmx.net>
Date: Mon, 5 Oct 2020 12:39:57 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <CADK1yX+0EDTuZ2Sg20_xJH02zLC15Ks1jcYR5zfECdnUBsfUFQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Subject: Re: [PHP-DEV] RFC: Support for multi-line arrow functions
From: a.leathley@gmx.net (Andreas Leathley)

On 05.10.20 12:15, Deleu wrote:
> To me that seems like a great argument in favour of the proposal. If you=
'll
> want all variables to be imported (which in this case makes completely
> sense), then `fn() {}` or `fn() =3D> {}` is much less verbose and inline=
 with
> the mentality to reach for short closures. We reach for short closures t=
o
> avoid `use()` and convey that the outer process is intertwined with the
> inner process. `fn()` allows to strengthen the concept that there's no r=
eal
> separation between running SQL stuff in a `callable` that wraps a databa=
se
> transaction.

Not necessarily: the arrow functions were specifically implemented for
very short anonymous functions with a return value. Making them more and
more like the existing "function" syntax would lead to having two
different ways of defining anonymous functions that mainly differentiate
themselves by including the parent scope by default or not.

I like the "function () use (*)" suggestion because it is explicit and
opt-in. A shorter syntax like "fn () {}" is less clear, and it could
lead to many people always using fn just because it is faster to write
(and less to think about), which then could lead to unintended side
effects because variables are being copied from the parent scope each
time. When you see a usage of "fn () {}" while reading code you would
not know if the person used it because it was faster to write, or if the
parent scope variables are really needed.