Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98201
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.51 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <f630636f-d616-45f1-cb01-7b5805b2667d@garfieldtech.com>
References: <CAFMT4Nrt7XPMnELoAGLu=sSRCTCtzPCTaSE8HJjKfHjDXOXU_A@mail.gmail.com>
 <CAFMT4Nq_vbCRmMZ2OSDN7_VqGG6UR6PTNevz3DWLF9K8MODMYg@mail.gmail.com>
 <CAFMT4NoxVT3JGLmT-8Vj5R4c-h-m9xK20nG3vQHyBKx3aNX3Og@mail.gmail.com> <f630636f-d616-45f1-cb01-7b5805b2667d@garfieldtech.com>
Date: Sat, 4 Feb 2017 14:30:26 -0700
Message-ID: <CAFMT4NrO2dMXChKUKGCeuW0OTqCUmQaoiw1RhHt=0+-p7zFb=A@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Re: [RFC][Discuss] Arrow Functions
From: levim@php.net (Levi Morrison)

> And then there's the extra typing and visual space taken up, which is not
> something to dismiss entirely.  Also, as someone else mentioned this syntax
> *seems* like it would support nesting. Compare the following:
>
> $x = function($a) => function($b) => function($c) => $a * $b * $c;
> $y = fn($a) => fn($b) => fn($c) => $a * $b * $c;
> $z = |$a| => |$b| => |$c| => $a * $b * $c;
>
> print $x(1)(2)(3); // prints 6
>
> Which of these is more readable?  Id' argue it's not $x.

In a past version the RFC included an example of chaining. The current
version doesn't show an example, but does say it is possible. To be
clear:

    $x = fn($a) => fn($b) => fn($c) => $a * $b * $c;

Is supported in the current implementation. It would similarly be
supported in the `|params| => expr` notation.