Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113742
MIME-Version: 1.0
References: <88c9eb5f-f80c-4869-b7f8-1b58b9e2eaa3@www.fastmail.com>
In-Reply-To: <88c9eb5f-f80c-4869-b7f8-1b58b9e2eaa3@www.fastmail.com>
Date: Wed, 24 Mar 2021 18:01:58 +0100
Message-ID: <CAF+90c9PRmK1FM_uUO3qMhhvMybY4z_aZkmMO53TVfuy--U32g@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000b9bebe05be4b42d4"
Subject: Re: [PHP-DEV] [RFC] Auto-capture multi-line closures and short
 functions take 2
From: nikita.ppv@gmail.com (Nikita Popov)

--000000000000b9bebe05be4b42d4
Content-Type: text/plain; charset="UTF-8"

On Wed, Mar 24, 2021 at 5:20 PM Larry Garfield <larry@garfieldtech.com>
wrote:

> Greetings, Internalians.
>
> Some months back I proposed an RFC for short functions.
>
> https://wiki.php.net/rfc/short-functions
>
> After some discussion, I put it on hold to ensure that it was compatible
> with the other discussion floating about around an alternate syntax for
> multi-line closures that did auto-capture.  It's important that the syntax
> of both proposals is consistent.
>
> Nuno Maduro and i have talked recently and worked out the syntax that is
> consistent between both proposals.  That takes 'fn' off the table for
> short-functions, for reasons discussed in both RFCs.
>
> To that end, I offer:
>
> 1) The updated short-functions RFC:
> https://wiki.php.net/rfc/short-functions
>
> 2) A new RFC, code by Nuno, for auto-capturing multi-statement closures:
> https://wiki.php.net/rfc/auto-capture-closure
>
> These are separate RFCs and at this time we plan to send them to separate
> votes, but I list them together to demonstrate that they have been
> developed in a mutually-compatible way.
>
> Further details in the auto-capture-closure RFC.
>

Could you please create two separate threads for these RFCs?

Nikita

--000000000000b9bebe05be4b42d4--