Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109743
MIME-Version: 1.0
References: <2677cdc6-309c-4e4e-9cd9-12ff2a90c1e1@www.fastmail.com>
In-Reply-To: <2677cdc6-309c-4e4e-9cd9-12ff2a90c1e1@www.fastmail.com>
Date: Tue, 21 Apr 2020 10:59:52 +0200
Message-ID: <CAF+90c-aXG5pVhnF_GC2gsEAYHW_qcowy2hJVf22AQWZJYi4+w@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000000d5e4305a3c93edc"
Subject: Re: [PHP-DEV] [RFC] Function pipe operator
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000000d5e4305a3c93edc
Content-Type: text/plain; charset="UTF-8"

On Tue, Apr 21, 2020 at 3:39 AM Larry Garfield <larry@garfieldtech.com>
wrote:

> Hello fine people of Internals!
>
> I've been commenting on other RFCs enough lately that I should probably
> put myself through the wringer, too.  I therefore offer this RFC to add a
> function pipe operator, as seen in a number of other languages:
>
> https://wiki.php.net/rfc/pipe-operator-v2
>
> A patch is available here:
>
> https://github.com/php/php-src/pull/5425
>
> Although I have one or two bits of it that I could use feedback on.  (Let
> me know over on GitHub.)
>
> It's deliberately a very small, lightweight, and targeted change.  The
> Future Work section suggests possible additions for later, but this is as
> much as my meager skills can manage for the moment.
>
> My enormous thanks to Sammy K Powers and Levi Morrison for their copious
> hand-holding in my first foray into php-src.
>
> *dons flame retardant suit*
>

I like the basic idea, but don't think it makes sense to introduce the
syntax *before* we have first-class support for partial function
application. Without it, you're forced to use PHP's awkward callable
syntax, which imho makes for a regression over writing things the normal
way.

Nikita

--0000000000000d5e4305a3c93edc--