Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:97883
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAFMT4Np4zPjDKswAcjA_TkJ70yMEzrRH2SJk_h1k26HnjMyuoA@mail.gmail.com>
References: <CAESVnVoBrtfWGF-Be+uXWwLNO3=JzuLBXyhW0Dpo-NvoskofQw@mail.gmail.com>
 <CAFMT4Np4zPjDKswAcjA_TkJ70yMEzrRH2SJk_h1k26HnjMyuoA@mail.gmail.com>
Date: Thu, 19 Jan 2017 15:17:50 -0700
Message-ID: <CAObuZdsO3+n4AOPuAFxRv-Z3CB9rTdW3p0Lzg5mN0+gSNOXBwg@mail.gmail.com>
To: Levi Morrison <levim@php.net>
Cc: Sara Golemon <pollita@php.net>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113d2cd866d4e9054679e7f1
Subject: Re: [PHP-DEV] Pipe Operator v2
From: derokorian@gmail.com (Ryan Pallas)

--001a113d2cd866d4e9054679e7f1
Content-Type: text/plain; charset=UTF-8

On Thu, Jan 19, 2017 at 5:54 AM, Levi Morrison <levim@php.net> wrote:

> On Wed, Jul 20, 2016 at 5:42 PM, Sara Golemon <pollita@php.net> wrote:
> > With the branching of 7.1, and after some reflection on the previous
> > feedback, I'd like to reopen discussion of the Pipe Operator RFC
> > https://wiki.php.net/rfc/pipe-operator which I had previously put on
> > hold.  I've changed much of the argument wording of the proposal, but
> > not the substantive feature set.  If you still feel it's unworkable,
> > I'd like to encourage you to respond with what you think would make it
> > workable (if anything).  Thanks.
> >
> > -Sara
> >
> > --
> > PHP Internals - PHP Runtime Development Mailing List
> > To unsubscribe, visit: http://www.php.net/unsub.php
>
> I've talked to you about this RFC off-list, but I figured I should
> mention it on-list as well. I think we should make `|>` and `$$` two
> independent operators that work well together (rather than only
> together).
>
> The `|>` symbol would be the piping operator with these semantics:
>
>     1. Evaluate the left-hand side.
>     2. Evaluate the right-hand side. Assert that the result is callable.
>     3. Pass the result from 1. as the single argument to 2.
>
> When you say assert the right hand side is callable, does that mean to
call an object method, you would do [$obj, 'method']? What about functions,
is it just the name like $str |> trim, or is it $str |> trim()? Neither
makes sense to me in the context of PHP since methods/functions are named
objects, which is why when you pass a callback you have to give the string
name of the function instead of just the name of the function, IE
array_filter($arr, 'trim') vs array_filter($arr, trim).

--001a113d2cd866d4e9054679e7f1--