Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99541
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mindplay.dk from 209.85.192.173 cause and error)
MIME-Version: 1.0
In-Reply-To: <3C763609-54FC-480B-AE95-94A1873226E0@me.com>
References: <CAFMT4Npoo_ZrRk-kk4C6KHYEtV93pU7Wmh0FhaPi6Z-9qkObaQ@mail.gmail.com>
 <4077c099-2247-c3c1-7dee-02a6b25f8586@fleshgrinder.com> <CAObuZdtHXp=icU_aB8dWyjbzW-yZ0sSTW6ObmEsxTuvR679-Fw@mail.gmail.com>
 <CAObuZdvck_w5iEeH5Sz23pDS1T727gtN7pn8XCiPWBvqVWR5Ag@mail.gmail.com>
 <CAObuZdvYX8Yr4KQnzJNeF8CSJVwpxuDevV+6=w_J5J9gx5R8HQ@mail.gmail.com>
 <559b73f7-c40f-e593-f0e1-51b56210d7cb@telia.com> <2053A608-6B66-42FB-A6D7-7CC64E94DA6A@koalephant.com>
 <4FBDE643-1EBC-485A-A39F-7E28C5D4807A@koalephant.com> <e1c608a0-d046-d3a8-a360-d33c3aa75666@telia.com>
 <034f3ebf-95b8-a7cf-1279-77c7cf0424d7@gmail.com> <46143e7c-ef75-7c05-eaa9-98c8f3b405f1@telia.com>
 <CAESVnVrLG4nRrcm7MYAQutb4umLq=FkGo2CWHYqHw+bYo72Bsg@mail.gmail.com>
 <d45a3327-59d4-5c93-1425-70cc2d08a87e@telia.com> <CAESVnVpQtLXhKnUn2EE4s7rZn11r5Kpj2zOSOKRCWFaxaeOrjg@mail.gmail.com>
 <b1105f90-91e9-e61a-b96b-5078c337ab5c@telia.com> <b47c4379-109c-c289-1077-b42ea40fe19f@telia.com>
 <ca6f11d0-5da3-757c-7acd-4acd79a876f1@fleshgrinder.com> <5fe1eefe-1c4f-4c31-c975-ab6c768c977c@telia.com>
 <E56D1F4A-6DC7-47DA-BAD6-1722E017B048@me.com> <CADqTB_jDmFZZc3ah=J8F99P77qnuWVgXS5UwXgrbartCp5B+UQ@mail.gmail.com>
 <3C763609-54FC-480B-AE95-94A1873226E0@me.com>
Date: Sun, 18 Jun 2017 20:48:58 +0200
Message-ID: <CADqTB_hU+38TOHdaukhGBS-2NPq-PNSci1h078TPOGbE7WcmWg@mail.gmail.com>
To: Ilija Tovilo <ilija.tovilo@me.com>
Cc: =?UTF-8?Q?Bj=C3=B6rn_Larsson?= <bjorn.x.larsson@telia.com>, 
	Fleshgrinder <php@fleshgrinder.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="001a1137111aa8af8f05524078bc"
Subject: Re: [PHP-DEV] [RFC]Discuss] Syntax for Arrow Functions
From: rasmus@mindplay.dk (Rasmus Schultz)

--001a1137111aa8af8f05524078bc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I understand it's not ambiguous to the parser if it's a keyword.

I was referring to the visual ambiguity - the fn($x) part of the syntax is
indistinguishable from a function-call.


On Sun, Jun 18, 2017 at 8:42 PM, Ilija Tovilo <ilija.tovilo@me.com> wrote:

> > I don't agree that the fn keyword solves the ambiguity problem - it loo=
ks
> > exactly like a function call.
>
>
> Right. But it does solve the ambiguity if `fn` is a keyword which is what
> the RFC suggests.
>
>
> > On 18 Jun 2017, at 18:40, Rasmus Schultz <rasmus@mindplay.dk> wrote:
> >
> > I don't agree that the fn keyword solves the ambiguity problem - it loo=
ks
> > exactly like a function call.
> >
> > As for the backslash, my honest reaction is, ugh, please, no more
> > backslashes - PHP (and every other language) uses backslashes for
> escaping
> > in strings, it already looks pretty awkward in namespaces, this won't
> help.
> >
> >
> > On Sun, Jun 18, 2017 at 12:58 PM, Ilija Tovilo <ilija.tovilo@me.com>
> wrote:
> >
> >> The backslash has actually been one of the earlier options if I rememb=
er
> >> correctly.
> >> I definitely prefer the `fn` keyword as it=E2=80=99s only one characte=
r more but
> >> adds a better visual hint to the arrow function.
> >>
> >> I=E2=80=99m also not sure why we=E2=80=99d choose a different arrow (`=
=3D=3D>` or `~>`) when
> >> the ambiguity is solved through either a the backslash or the `fn`
> keyword.
> >>
> >>
> >>> On 15 Jun 2017, at 17:00, Bj=C3=B6rn Larsson <bjorn.x.larsson@telia.c=
om>
> >> wrote:
> >>>
> >>> Den 2017-06-15 kl. 15:34, skrev Fleshgrinder:
> >>>
> >>>> On 6/15/2017 3:29 PM, Bj=C3=B6rn Larsson wrote:
> >>>>> Seems like the constraints on this feature makes it hard to fly, i.=
e.
> >>>>> 1. Not a hackish implementation
> >>>>> 2. Non ambiguous syntax
> >>>>> 3. Easy to parse & use syntax for the human
> >>>>>
> >>>>> HackLang then prioritised 2 & 3 making the end-users happy, but
> >>>>> had to sacrifise a clean implementation. Any clue if this was a one=
-
> >>>>> time effort once it was done or something with a lot of drawbacks
> >>>>> in terms of maintenance, performance, evolution etc?
> >>>>>
> >>>>> r//Bj=C3=B6rn
> >>>>>
> >>>> On Reddit someone proposed the following syntax:
> >>>>
> >>>>    \() =3D> echo 'Hello, World'
> >>>>
> >>>> It is used by Haskell if I remember correctly and should not be
> >>>> ambiguous since `(` is not allowed in names of classes or functions.
> It
> >>>> actually aligns well with functions that are called with a
> >>>> fully-qualified name (e.g. `\printf('')`).
> >>>>
> >>>> Not sure if it would still require hacks though.
> >>>>
> >>> So applying that one on Sara's example becomes with some
> >>> options for the arrow:
> >>> 8. $someDict->map(\($v) =3D> $v * 2)->filter(\($v) =3D> $v % 3);
> >>> 9. $someDict->map(\($v) =3D=3D> $v * 2)->filter(\($v) =3D=3D> $v % 3)=
;
> >>> 10. $someDict->map(\($v) ~> $v * 2)->filter(\($v) ~> $v % 3);
> >>>
> >>> Interesting :)
> >>>
> >>> r//Bj=C3=B6rn
> >>>
> >>> --
> >>> PHP Internals - PHP Runtime Development Mailing List
> >>> To unsubscribe, visit: http://www.php.net/unsub.php <
> >> http://www.php.net/unsub.php>
> >>
>
>

--001a1137111aa8af8f05524078bc--