Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98175
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain me.com designates 17.172.80.96 as permitted sender)
Date: Sat, 04 Feb 2017 11:09:00 +0100
To: Stephen Reay <php-lists@koalephant.com>
Cc: internals <internals@lists.php.net>
Message-ID: <119a1b84-edff-424c-99ba-fd14cbc23ce4@Spark>
In-reply-to: <77287A6A-C3E9-4C93-A1F2-2899DAEA8738@koalephant.com>
References:
 <CAFMT4Nrt7XPMnELoAGLu=sSRCTCtzPCTaSE8HJjKfHjDXOXU_A@mail.gmail.com>
 <CAFMT4Nq_vbCRmMZ2OSDN7_VqGG6UR6PTNevz3DWLF9K8MODMYg@mail.gmail.com>
 <CAFMT4NoxVT3JGLmT-8Vj5R4c-h-m9xK20nG3vQHyBKx3aNX3Og@mail.gmail.com>
 <CAEUnE0exyYOr5UytWmEsmXp0MirH1VqvMT4KQMdb=aT9DobK4w@mail.gmail.com>
 <CAEsg9X2v8tFQ0MkR_Qo=C3LWMK2vnXkh+q+zhFmp-eMoUSeD6w@mail.gmail.com>
 <19.45.38491.677D4985@pb1.pair.com>
 <CAFMT4Nruv6-h_7QoXtJoCPN5atU-fB_BY7RK45wZmkXri7hDrg@mail.gmail.com>
 <611b72db-420f-4963-ab92-0ddf977a0aaa@Spark>
 <9AF0D2F6-D668-418C-8B96-3320D9D245ED@trowski.com>
 <5722B01C-A621-4C13-B34B-383B0D9753F9@koalephant.com>
 <22B18CB2-0383-4D4D-9B55-91A748725AC9@trowski.com>
 <77287A6A-C3E9-4C93-A1F2-2899DAEA8738@koalephant.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary=5895a8f5_327b23c6_4609
Subject: Re: [PHP-DEV] [RFC][Discuss] Arrow Functions
From: ilija.tovilo@me.com

--5895a8f5_327b23c6_4609
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi Stephen

> Using type hints is a part of the language. It even has benefits that I=
 can absolutely see being used here:
>
> array=5Fmap(function(=46oo =24x) =3D> =24x->bar());
>
> If =46oo is a class/interface with a method of bar, your IDE can know t=
hat it's a valid method to call.
>
> That of course is in addition to the benefit of getting useful type err=
ors from PHP itself.

I agree but think that this is the wrong approach. PHP is a weakly typed =
language. Doesn=E2=80=99t it seem wrong that you have to specify types in=
 more places than in many modern strongly typed languages=3F Look at Swif=
t for example. IMHO, the right approach would be to implement proper clos=
ure type hints. This has the benefit of letting the callee specify what k=
ind of closure is expected (who knows that much better than the caller an=
yway) while allowing for IDE autocompletion.

Nonetheless, specifying type hints on the closures is what we do right no=
w. The approach Levi suggested works well with that.

> So we should instead use syntax already used for bit wise OR, and furth=
er confuse the situation when the function has no parameters and reusing =
the logical OR operator. Brilliant.
>
> This is still a function, it has slightly different semantics, just lik=
e how a regular function, a class instance method and a static class meth=
od have slightly different semantics: we still use the function keyword f=
or all of those.
>
> The static keyword is used for functions, class static properties, stat=
ic variables and even static closures: it's semantics are slightly differ=
ent for each case but we reuse the same keyword.

As Levi already mentioned, this argument is similar to claiming reusing t=
he =60function=60 keyword could be confusing. Both should be perfectly cl=
ear to anyone who is serious about programming. I think we can expect for=
 programmers to get informed about new features before using them. This s=
eems to work for any other language. Also, it=E2=80=99s not like the sugg=
ested syntax is something we=E2=80=99ve never seen before. Ruby has it, R=
ust has it (or something similar at least). The rest personal preference =
I suppose.

I can see how people like =60function=60 more because of consistency. I l=
ike =60=7C=7C =3D> expr=60 more because of readability (for me, the less =
reading the better :P).

=40Levi Maybe it would be best to vote for the closure syntax=3F My least=
 favourite option is better than the R=46C getting shot down because peop=
le dislike the syntax.


--5895a8f5_327b23c6_4609--