Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93036
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.215.51 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <AA.0D.03860.787F7275@pb1.pair.com>
References: <CAESVnVpa5j=fagr-wm5+DzKKX=wzTN1p8+Kv3-KtGpuyH51b0A@mail.gmail.com>
	<4fc01507-3d07-2309-a4e4-4cad7325249b@gmail.com>
	<AA.0D.03860.787F7275@pb1.pair.com>
Date: Mon, 2 May 2016 21:49:25 -0700
Message-ID: <CAESVnVoU3L2d5De4TC0WKyF=dfHs+aWonFccn11xvhYJtRvSQA@mail.gmail.com>
To: Stephen Coakley <me@stephencoakley.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Pipe Operator
From: pollita@php.net (Sara Golemon)

On Mon, May 2, 2016 at 5:57 PM, Stephen Coakley <me@stephencoakley.com> wrote:
> Could you use a closure instead to accomplish this? (Again yes, Sara could
> you clarify if this is permitted?)
>
> $ret = scandir($arg)
>         |> array_filter($$, function($x) { return $x !== '.' && $x != '..';
> })
>         |> array_map(function ($x) use ($arg) { return $arg . '/' . $x; },
> $$)
>         |> (function($fileList) {
>                if (someCheck($fileList)) {
>                    something();
>                }
>                return $fileList;
>            })($$)
>         |> getFileArg($$)
>         |> array_merge($ret, $$);
>
You could, but IMO you lose a lot of the elegance if you go that
route.  This syntax works best when you have a series of functions
which /don't/ have failure cases (and many many functions don't), or
who fail via exceptions.

Using current syntax, the above would look like:

$ret = array_merge($ret, getFileArg(function($fileList) {
     if (someCheck($fileList)) { something(); }
     return $fileList;
   })(array_map(function($x) use ($arg) { return $arg . '/' . $x; },
     array_filter(scandir($arg), function($x) { return $x !== '.' &&
$x !== '..'; }))
  )));

It's way more readable in the pipe syntax version, but it's
overloading a single statement in both places.

-Sara