Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99369
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain telia.com from 81.236.60.155 cause and error)
To: Rowan Collins <rowan.collins@gmail.com>
References: <CAFMT4Npoo_ZrRk-kk4C6KHYEtV93pU7Wmh0FhaPi6Z-9qkObaQ@mail.gmail.com>
 <DM3PR18MB07641E547AD2FA1DFA5BEF65DEF60@DM3PR18MB0764.namprd18.prod.outlook.com>
 <6357d97c-3f2e-4cf8-cb1f-cb7f7ccccf7c@telia.com>
 <CADqTB_hNob7ZiGX66gJEpCymrZJqqsZ1uAGnYg6v6sbrwx1-KQ@mail.gmail.com>
 <7eaef49b-bf60-9aa1-e812-8430164e3178@garfieldtech.com>
 <f5992058-aecd-8bc4-08f8-2bfe722cd41e@fleshgrinder.com>
 <3F920987-38CB-42DD-888D-824430C36F14@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Message-ID: <2f9e73c9-444a-11d0-459a-e261ea8a7080@telia.com>
Date: Mon, 5 Jun 2017 20:11:12 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <3F920987-38CB-42DD-888D-824430C36F14@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: sv
Subject: Re: [PHP-DEV] [RFC]Discuss] Syntax for Arrow Functions
From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=)



Den 2017-06-05 kl. 19:55, skrev Rowan Collins:
> On 5 June 2017 18:17:06 BST, Fleshgrinder <php@fleshgrinder.com> wrote:
>> Could someone explain me again what the problem with the simple
>> fat-arrow and normal parenthesis is? Cannot find it anymore (too many
>> messages in too many thread I guess). I would guess that it has to do
>> with the arbitrary look-ahead that is required to check for the fat
>> arrow before the lexer knows that this is a short closure and not some
>> parenthesis that simply groups something.
> I think it's not just a case of implementation problems, it's actually ambiguous with current syntax:
>
> $foo = array( ($x) => 42 );
>
> Sure, those inner brackets are redundant, so it's not likely to break much actual code, but it's kind of weird to have this one case magically turn into a closure, when anything else you put in those brackets would just be used as the array key:
>
> $foo = array( f($x) => 42 );
> $foo = array( ($x+1) => 42 );
> $foo = array( (42) => $x );
> $foo = array( (X) => 42 );
> $foo = array( ($x) => 42 );
> $foo = array( ("$x") => 42 );
>
> Even if we could teach the parser to understand it, I'd personally be against it for the difficulty of *humans* parsing it. I find shorthand closures hard enough to read anyway, especially when people suggest things like ($x) => ($y) => $x * $y * $z;
>
> Regards,
>
+1, think you nailed it here :) One of the reasons I prefer the ==> syntax.

r//Björn