Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104708
Date: Thu, 14 Mar 2019 06:16:59 +0000
User-Agent: K-9 Mail for Android
In-Reply-To: <CAEsg9X0KD4F-CdK7WwjG6JXhmqauKBaie799F+Nkqp7iTwjidA@mail.gmail.com>
References: <CAF+90c9YZcrquGfS4h3x1a+codkCFLarAThsOXcN69RCTvbAFA@mail.gmail.com> <CAEsg9X0KD4F-CdK7WwjG6JXhmqauKBaie799F+Nkqp7iTwjidA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: internals@lists.php.net
Message-ID: <46ECA6BB-03DE-4047-A464-6C5F697CAE73@gmail.com>
Subject: Re: [PHP-DEV] [RFC] Arrow functions / short closures
From: rowan.collins@gmail.com (Rowan Collins)

On 14 March 2019 04:01:54 GMT+00:00, David Rodrigues <david=2Eproweb@gmail=
=2Ecom> wrote:
>1=2E Your example with "($x) =3D> $x" consider the use of "$x =3D> $x", b=
ut
>not
>specifically "($x) =3D> $x"=2E I mean: maybe it can accept "($x) =3D> $x"=
 but
>not
>"$x =3D> $x" because of the array conflict (as mentioned), and with that
>we
>avoid to create a new keyword "fn"=2E So parentheses is required=2E


I don't think this helps, because you can put brackets around any expressi=
on, for precedence, and any expression can appear on the left of an array l=
iteral:

$foo =3D [ ($bar + 1) * 2 =3D> $baz ];

So the following, while redundant, is currently valid:

$foo =3D [ ($bar) =3D> $baz ];

Regards,

--=20
Rowan Collins
[IMSoP]