Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98180
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 16:48:27 +0100
To: Stephen Reay <php-lists@koalephant.com>
Cc: internals <internals@lists.php.net>
Message-ID: <c7e6389b-dbfb-452f-8349-7e98be6a1985@Spark>
In-reply-to: <75d6f740-92ee-4906-a668-f8c83039d300@Spark>
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>
 <119a1b84-edff-424c-99ba-fd14cbc23ce4@Spark>
 <B691FFA7-5A11-4797-90F4-E41EC5C55DC7@koalephant.com>
 <75d6f740-92ee-4906-a668-f8c83039d300@Spark>
MIME-version: 1.0
Content-type: multipart/alternative; boundary=5895f824_65048f95_4609
Subject: Re: [PHP-DEV] [RFC][Discuss] Arrow Functions
From: ilija.tovilo@me.com

--5895f824_65048f95_4609
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Ah, my example was of course wrong again -.-

The caller should=E2=80=99ve looked like this (although I think you get t=
he point):

=60=60=60Swift
fetchUsers =7B users in
=C2=A0 =C2=A0// =60users=60 is inferred to be an=C2=A0array of=C2=A0=60Us=
er=60s
=7D
=60=60=60

Regards


On 4 =46eb 2017, 16:41 +0100, ilija.tovilo=40me.com, wrote:
> Hey Stephen
>
> > You don't *have to* specify types at all. If you want to use PHP with=
out verifying/requiring types, thats your prerogative, but given the rece=
nt improvements to allow scalar type hinting, I think it=E2=80=99s a mist=
ake to say that *any* use of type hints is =E2=80=9Cnot recommended=E2=80=
=9D.
>
> Sure you don=E2=80=99t but then you loose all the benefits of specifyin=
g types. We want typing but only if we don=E2=80=99t have to specify type=
s all over the place. I really dislike having to add PHPDocs everywhere j=
ust to get some proper autocompletions.
>
> > I'm not sure if you've mixed up your terms of if I'm too tired but I =
don't understand what you mean here. The short arrow function *is* the ca=
llee, and that=E2=80=99s where you=E2=80=99re suggesting we shouldn=E2=80=
=99t use type hints.
>
> Sorry, that was confusing. I was thinking of a situation like this one:=

>
> =60=60=60Swift
> func fetchUsers(callback: (=5BUser=5D) -> Void) =7B
> =C2=A0 =C2=A0 ...
> =7D
> =60=60=60
>
> So, the callee (=60fetchUsers=60) defines what the provided closure mus=
t look like.
> The caller, on the other hand, doesn=E2=80=99t have to specify that aga=
in as you=E2=80=99re just repeating yourself.
>
> =60=60=60Swift
> fetchUsers =7B user in
> =C2=A0 =C2=A0// =60user=60 is inferred to be a =60User=60 object
> =7D
> =60=60=60
>
> So I don=E2=80=99t think the burden of providing typing information sho=
uld be on the caller providing the closure.
>
> > The whole issue with that is that using a pipe character could make t=
hings much less clear/readable if the already established use of pipe for=
 =E2=80=9Ctype unions=E2=80=9D (currently used in multi-catch) were to be=
 implemented for general type hint usage.
> >
> > Note: I=E2=80=99m not saying it=E2=80=99s not possible, but it=E2=80=99=
s *much* less readable, and any =E2=80=9Csolution=E2=80=9D just adds more=
 characters, which is apparently the only reason to not use function(=24f=
oo) =3D> =24foo in the first place.
>
> But again, that=E2=80=99s personal preference. I like short a precise a=
nd think it=E2=80=99s more readable. Not everyone=E2=80=99s the same.
>
> > =C2=A0=46or most people readability isn't just about the number of ch=
aracters.
>
> A lot of the time it is. Brains are very good at recognising patterns, =
they don=E2=80=99t need large keywords for that.
> As for me, I think it just adds clutter to the actual logic that I=E2=80=
=99m interested in.
>

--5895f824_65048f95_4609--