Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126340
Feedback-ID: i8414410d:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Fri, 07 Feb 2025 13:48:02 -0600
To: "php internals" <internals@lists.php.net>
Message-ID: <4d494e02-62de-4d4e-9e83-b4483758b3cb@app.fastmail.com>
In-Reply-To: <65d875b7-8ea7-43ff-9dbc-a1e335073115@gmx.de>
References: <de8140ab-0941-45cd-ba20-4aece2f69aea@app.fastmail.com>
 <65d875b7-8ea7-43ff-9dbc-a1e335073115@gmx.de>
Subject: Re: [PHP-DEV] [RFC] Pipe Operator (again)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: larry@garfieldtech.com ("Larry Garfield")

On Fri, Feb 7, 2025, at 10:51 AM, Christoph M. Becker wrote:

>> Of particular note, since the last RFC I have concluded that a compos=
e operator is a necessary complement to a pipe operator.  However, it's =
also going to be notably more work, and the two operators don't actually=
 interact at all at the code level, so since people keep saying "Small R=
FCs!", here's a small RFC. :-)
>
> Fair enough.  And with the pipe operator, one might live without a
> compose operator, e.g.
>
>   $f1 =3D fn($x) =3D> 2 * $x;
>   $f2 =3D fn($x) =3D> $x + 3;
>   // $f3 =3D $f2 =E2=88=98 $f1
>   $f3 =3D fn($x) =3D> $x |> $f1 |> $f2;
>
> Christoph

The v2 RFC took that position, that compose was easy enough to emulate v=
ia pipe.  Indeed, pipe and compose can both be implemented in terms of e=
ach other.  However, since the previous RFC I've concluded[1] that both =
are sufficiently useful that we really out to include both of them.  PIp=
es are just way easier to implement in practice. :-)

--Larry Garfield

[1] https://peakd.com/hive-168588/@crell/aoc2021-review