Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118175
MIME-Version: 1.0
References: <e506a378-2060-4cc1-98a6-3c9c7c0bd903@www.fastmail.com>
In-Reply-To: <e506a378-2060-4cc1-98a6-3c9c7c0bd903@www.fastmail.com>
Date: Mon, 4 Jul 2022 11:47:03 +0200
Message-ID: <CAOWwgpmNMmGOE+MTuRkOiqkgDZaO+-GO53-1SWFJhQ=PiHH6cg@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>, Arnaud Le Blanc <arnaud.lb@gmail.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000ee113e05e2f79e46"
Subject: Re: [PHP-DEV] [RFC][Vote] Auto-capture closures
From: nicolas.grekas+php@gmail.com (Nicolas Grekas)

--000000000000ee113e05e2f79e46
Content-Type: text/plain; charset="UTF-8"

Hi there,


Greetings, Internalians.
>
> The vote for auto-capture closures is now open.  It will run until 15 July.
>
> https://wiki.php.net/rfc/auto-capture-closure
>

Thanks for the RFC, I voted yes as I think the optimized auto-capturing
logic is sound.

Having "function()" still be a first-class citizen is also important to me
as there are cases where one might prefer the explicit nature of capturing,
so I join Rowan on this "rhetoric" topic.

I'm just wondering if there could be a way to enable the auto-capture
optimization for arrow functions. Having three kinds of rules for capturing
feels too much, especially when there are that subtles for short closures.
Maybe a deprecation could be possible for affected arrow functions?

Nicolas

--000000000000ee113e05e2f79e46--