Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99367
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.54 as permitted sender)
Date: Mon, 05 Jun 2017 18:55:25 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <f5992058-aecd-8bc4-08f8-2bfe722cd41e@fleshgrinder.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>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: internals@lists.php.net
Message-ID: <3F920987-38CB-42DD-888D-824430C36F14@gmail.com>
Subject: Re: [PHP-DEV] [RFC]Discuss] Syntax for Arrow Functions
From: rowan.collins@gmail.com (Rowan Collins)

On 5 June 2017 18:17:06 BST, Fleshgrinder <php@fleshgrinder=2Ecom> 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)=2E 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=2E=20

I think it's not just a case of implementation problems, it's actually amb=
iguous with current syntax:

$foo =3D array( ($x) =3D> 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 i=
nto a closure, when anything else you put in those brackets would just be u=
sed as the array key:

$foo =3D array( f($x) =3D> 42 );
$foo =3D array( ($x+1) =3D> 42 );
$foo =3D array( (42) =3D> $x );
$foo =3D array( (X) =3D> 42 );
$foo =3D array( ($x) =3D> 42 );
$foo =3D array( ("$x") =3D> 42 );

Even if we could teach the parser to understand it, I'd personally be agai=
nst it for the difficulty of *humans* parsing it=2E I find shorthand closur=
es hard enough to read anyway, especially when people suggest things like (=
$x) =3D> ($y) =3D> $x * $y * $z;

Regards,

--=20
Rowan Collins
[IMSoP]