Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117917
Message-ID: <036bb10b-3e21-8516-db56-75a8c0fa964e@demon-angel.eu>
Date: Sun, 12 Jun 2022 19:54:06 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.9.1
Reply-To: mark@demon-angel.eu
To: internals@lists.php.net
References: <2b35605f-8da8-46b1-aec3-00bd1bfe47fd@www.fastmail.com>
 <2279cbd2-fcfe-460f-97f9-0029b7b043bb@www.fastmail.com>
In-Reply-To: <2279cbd2-fcfe-460f-97f9-0029b7b043bb@www.fastmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Short Closures 2, aka auto-capture take 3
From: mark@demon-angel.eu (Mark Baker)

On 12/06/2022 19:21, Larry Garfield wrote:
> On Thu, Jun 9, 2022, at 11:34 AM, Larry Garfield wrote:
>
> A little data:
>
> I used Nikita's project analyzer on the top 1000 projects to get a rough sense of how long-closures are used now.  All usual caveats apply about such survey data.  I was specifically looking at how many `use` statements a closure typically had, and how many statements it typically had.  Mainly, I am interested in how common "really long closures where the developer is likely to lose track of what is and isn't closed over" are.
>
> Total closures: 20052
> Total used variables: 11534
>
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.


-- 
Mark Baker

  _________
|.  \     \-3
|_J_/ PHP |
|| |  __  |
|| |m|  |m|

  I LOVE PHP