Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100791
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.220.175 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <98e7fff2-72ac-0430-72bb-099a021626f6@gmail.com>
References: <CAESVnVo4axBD86qLbXvq4Mb39Dgdx_RQ1rH3KEG8ToaF7CbDag@mail.gmail.com>
 <98e7fff2-72ac-0430-72bb-099a021626f6@gmail.com>
Date: Wed, 27 Sep 2017 15:56:07 -0400
Message-ID: <CAESVnVqN05VsX8dvnN39rdEo=8MkzSWtr=nhP27jY71HxRdn=g@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] Pre-draft for PipeOp v2
From: pollita@php.net (Sara Golemon)

On Thu, Sep 21, 2017 at 5:13 PM, Stanislav Malyshev <smalyshev@gmail.com> wrote:
> It'd be also nice then if we could have some syntax that allowed us to
> refer to functions/methods as callables - mostly for the benefit of the
> code readers and IDEs. I.e. you can do "hello" |> "strtoupper" and it's
> fine but it is not at all intuitive what you're doing sending one string
> into another. Same with "hello" |> [$this, 'bar']. Now, if we could do
> something like this:
> "hello" |> &{strtoupper}
> "hello" |> &{$this->bar}
>
Super-hacky implementation (that I wouldn't want to merge, but it
shows the syntax at work).

https://github.com/php/php-src/compare/master...sgolemon:lambda
which provides a form of both short-closures and partial functions.

Combined with also-super-hacky pipe diff from earlier, you get:

$x = "Hello"
  |> &{strtoupper($0)}
  |> &{ $0 . "world" }
  |> &{strrev($0)};

var_dump($x);
// string(10) "dlrowOLLEH"

-Sara