Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98145
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain kelunik.com from 81.169.146.162 cause and error)
MIME-Version: 1.0
In-Reply-To: <CAFMT4Nruv6-h_7QoXtJoCPN5atU-fB_BY7RK45wZmkXri7hDrg@mail.gmail.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>
Date: Fri, 3 Feb 2017 21:37:21 +0100
Message-ID: <CANUQDCgnSLeheJu2jYY5s6mthKzu=bDMNRNObrpOf46c=nLggw@mail.gmail.com>
To: Levi Morrison <levim@php.net>
Cc: Andrea Faulds <ajf@ajf.me>, internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=94eb2c09830eab88a00547a63fb4
Subject: Re: [PHP-DEV] Re: [RFC][Discuss] Arrow Functions
From: me@kelunik.com (Niklas Keller)

--94eb2c09830eab88a00547a63fb4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2017-02-03 21:23 GMT+01:00 Levi Morrison <levim@php.net>:

> On Fri, Feb 3, 2017 at 12:18 PM, Andrea Faulds <ajf@ajf.me> wrote:
> > Hi David,
> >
> > David Rodrigues wrote:
> >>
> >> Hello folks!
> >> I just not understand why "function" should be abbreviated. It's about
> >> "how
> >> less character better"? I don't see it too much on PHP. I guess that i=
s
> >> more simple keep what exists current "function", that all knows about
> >> (that
> >> should be better than the next example):
> >>
> >> $mapped =3D array_map(function($x) =3D> $x + $y); // vs current:
> >> $mapped =3D array_map(function($x) use($y) { return $x + $y });
> >
> >
> > I feel the same way. It would be nice to have shorter syntax, but it
> > sacrifices readability and familiarity here, and adds yet another new
> > keyword.
> >
> > It also feels inconsistent=E2=80=A6 isn't "fn" just short for "function=
"? Why is
> it
> > exclusive to the =3D> syntax?
>
> This is not exactly on topic... unless you are implying you'd prefer
> the `|$x| =3D> $x + $y`? Maybe you missed [this][1] message?
>

Why is using "function" instead of "fn" not on topic?

Thanks to everyone who has participated in the discussion thus far.
> Primarily the feedback has been directed at the `fn` keyword. Let me
> provide two benefits and drawbacks of using `fn` as a keyword:
>   1. `fn` is searchable in search engines and in our manual
>

Just as "php function" is, too:
http://php.net/manual/en/language.functions.php


>   2. Is more intuitive than just syntax
>

As is "function", too. With the added benefit that people are already
familiar with it.


> However, `fn` does have downsides:
>   1. Can break existing code
>

Which doesn't happen with reusing "function".


>   2. We already have a similar keyword `function`
>

Right, so why not use that?


> To that end, I'd like to gauge interest in a pure syntax based
> alternative that is similar to Rust and Ruby.
> Instead of:
>     fn(params) =3D> expr
> What about:
>     |params| =3D> expr
> This trades the advantages of the keyword for the advantages of pure
> syntax, and happens to be two characters shorter. To be explicit:
>     1. Preserves 100% backwards compatibility
>     2. Avoids having two keywords that both mean "function"
>     3. Is not easily searchable in engines or in the manual
>     4. Is a tad bit shorter
>

1, 2, and 3 are also solved by using "function".

4 is counting characters instead of focusing on readability.

There are more drawbacks to that syntax like no parameters looking pretty
weird: || =3D>

Regards, Niklas


>   [1]: http://news.php.net/php.internals/98136
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--94eb2c09830eab88a00547a63fb4--