Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120535
MIME-Version: 1.0
References: <CA+kxMuTTuk8rQhdAFqkUDmyP95F0dSYmZMUyD0NY4Ae+CPL0PA@mail.gmail.com>
In-Reply-To: <CA+kxMuTTuk8rQhdAFqkUDmyP95F0dSYmZMUyD0NY4Ae+CPL0PA@mail.gmail.com>
Date: Tue, 6 Jun 2023 16:26:08 +0200
Message-ID: <CA+hqhpehVOAg3q05YoLT40ndfEFFudVcmiMq0JVt0UjZycqxdQ@mail.gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] RFC [Discussion]: Closure self-reference
From: weirdan@gmail.com (Bruce Weirdan)

On Sat, Jun 3, 2023 at 9:11=E2=80=AFPM Dan Ackroyd <Danack@basereality.com>=
 wrote:
> I'm now opening the discussion for the Closure self-reference RFC:
> https://wiki.php.net/rfc/closure_self_reference

Looking at the syntax options on the RFC page, the following
explanation is not clear to me:

> * De-anonymize the function. This has a large aesthetic downside of appea=
ring to create the closure variable in the scope that the closure is declar=
ed in, rather than internal to the closure scope.

Does this mean that the variable wouldn't actually be created in the
enclosing scope, but someone may *think* it would?


--=20
  Best regards,
      Bruce Weirdan                                     mailto:weirdan@gmai=
l.com