Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113790
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Thu, 25 Mar 2021 18:16:49 +0100
References: <88c9eb5f-f80c-4869-b7f8-1b58b9e2eaa3@www.fastmail.com>
 <CAF+90c9PRmK1FM_uUO3qMhhvMybY4z_aZkmMO53TVfuy--U32g@mail.gmail.com>
 <CAPKYkKxTgHnzXKwkHi4qgJewY86vWFehrhN39fyrrK5KWNVvig@mail.gmail.com>
 <CAPrKfG6LojbeeaK+ddEBJX7vmG18F7Jo3mrwzEr709JKneESPw@mail.gmail.com>
 <43a2b198-ab3d-411a-b978-2924e6af4b13@www.fastmail.com>
To: php internals <internals@lists.php.net>
In-Reply-To: <43a2b198-ab3d-411a-b978-2924e6af4b13@www.fastmail.com>
Message-ID: <98882A42-D265-41E5-8C67-4A1B38A2E932@cschneid.com>
Subject: Re: [PHP-DEV] [RFC] Auto-capture multi-line closures and short
 functions take 2
From: cschneid@cschneid.com (Christian Schneider)

Am 25.03.2021 um 17:25 schrieb Larry Garfield <larry@garfieldtech.com>:
> So in conclusion, it seems the reasons closures weren't auto-capture =
always were:
>=20
> 1) Possible performance concerns that are no longer relevant.
> 2) Avoid surprise references.
> 3) Allow users to capture by value or by reference.
>=20
> Point 1 is no longer relevant as the engine has changed so much.
> Point 2 is no longer relevant since forever, since capture is by-val =
by default.
> Point 3 is only relevant in the cases where you need to capture by =
reference, which in practice it turns out are really quite rare.
>=20
> So, I would argue that all of the reasons for manual capture in the =
first place are no longer relevant, except in the edge case where you =
really do want to capture by reference.

While the discussion back then revolved a lot around performance and =
references I don't think

4) Local-as-default scoping and explicit captures are the PHP way and =
make it a better language

which was mentioned in this thread should be buried ;-)

- Chris