Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117925
To: internals@lists.php.net
Cc: mark@demon-angel.eu
Date: Mon, 13 Jun 2022 11:35:55 +0200
Message-ID: <827956617.0ifERbkFSE@arnaud-t490>
In-Reply-To: <036bb10b-3e21-8516-db56-75a8c0fa964e@demon-angel.eu>
References: <2b35605f-8da8-46b1-aec3-00bd1bfe47fd@www.fastmail.com> <2279cbd2-fcfe-460f-97f9-0029b7b043bb@www.fastmail.com> <036bb10b-3e21-8516-db56-75a8c0fa964e@demon-angel.eu>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [PHP-DEV] [RFC] Short Closures 2, aka auto-capture take 3
From: arnaud.lb@gmail.com (Arnaud Le Blanc)

On dimanche 12 juin 2022 19:54:06 CEST Mark Baker wrote:
> Did many of those closures use "pass by reference" in the use clause,
> because that's one real differentiator between traditional closures and
> short lambdas. There's also the fact that use values are bound at the
> point where the closure is defined, not where it's called (if they even
> exist at all at that point), although that's probably more difficult to
> determine.

Please note that auto-capture binds variables at function declaration. This is 
the case in Arrow Functions, and is inherited by this RFC.