Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99296
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.170 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <934DD9E3-FACE-4BE0-A40F-0B240FE5D186@gmail.com>
References: <CAFMT4Npoo_ZrRk-kk4C6KHYEtV93pU7Wmh0FhaPi6Z-9qkObaQ@mail.gmail.com>
 <934DD9E3-FACE-4BE0-A40F-0B240FE5D186@gmail.com>
Date: Wed, 31 May 2017 07:48:03 -0600
Message-ID: <CAFMT4NpDuBuj2d7yv-9upPz9zkLAXYgKBMPHAca3+JxV8-209Q@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC]Discuss] Syntax for Arrow Functions
From: levim@php.net (Levi Morrison)

On Wed, May 31, 2017 at 7:36 AM, Rowan Collins <rowan.collins@gmail.com> wrote:
> On 30 May 2017 18:58:14 BST, Levi Morrison <levim@php.net> wrote:
>>Internals,
>>
>>The previous discussion thread has died down significantly and so I'd
>>like to start a new one to refocus. This message has some redundant
>>information by design so people don't have to reference the other
>>thread so much.
>>
>>Based on the discussion there are a few different syntax choices
>>people liked. Overall it's a feature that people seem to want but
>>everyone seems to prefer a different syntax choice.
>
> I was just pondering alternative approaches to stop the => token being ambiguous, and wondered if surrounding the whole expression with braces could work:
>
> { => $bound * 2 }
> { $a, $b => $a * $b }
>
> I believe this eliminates the ambiguity with array notation, and is more concise than pretty much every alternative. I'm my opinion, grouping the arguments and body would make it more readable in context, as well.

This does not work. We permit expressions as statements and we also
allow empty blocks:

    {
        $a = $foo;
    }

These will conflict in the grammar.