Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105949
MIME-Version: 1.0
References: <CAOv67gumG=mdj1Nr=uXtRTSdxGOMEu8=TZizdpgf5AsoaRVGDg@mail.gmail.com>
In-Reply-To: <CAOv67gumG=mdj1Nr=uXtRTSdxGOMEu8=TZizdpgf5AsoaRVGDg@mail.gmail.com>
Date: Sun, 16 Jun 2019 08:46:47 +0300
Message-ID: <CAAwdEzDuwpVqFS1Rm4j3p6jzXgWoOiJi+YA-P5qn1AUkTnqXjg@mail.gmail.com>
To: Wes <netmo.php@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000007a93f8058b6a682d"
Subject: Re: [PHP-DEV][RFC] Alternative "use" syntax for Closures
From: drealecs@gmail.com (=?UTF-8?Q?Alexandru_P=C4=83tr=C4=83nescu?=)

--0000000000007a93f8058b6a682d
Content-Type: text/plain; charset="UTF-8"

Hi,

If at some point we would have multi-statement body arrow function, I would
assume that one option would be to have the closure done automatically, as
it is done now on the one-line arrow function.
If the values will not be implicitly captured, maybe a new syntax to
capture can be designed there, for multi-line arrow functions.
A way to scan variables is already implemented for the one-line and, I
guess, a way to scan for few lines could also be implemented easier for the
new syntax.

Alex


On Sun, Jun 16, 2019, 00:54 Wes <netmo.php@gmail.com> wrote:

> Hello PHP, I just published
>
> https://wiki.php.net/rfc/alternative-closure-use-syntax
>
> I would love your opinion on this
>
> I know it seems overkill and wrong to have two different syntaxes for the
> same thing, but I really believe that's all we need to fix one of the most
> hated PHP syntax bits.
>
> Thank you.
>
> Wes
>

--0000000000007a93f8058b6a682d--