Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126319
Precedence: bulk
MIME-Version: 1.0
References: <de8140ab-0941-45cd-ba20-4aece2f69aea@app.fastmail.com>
In-Reply-To: <de8140ab-0941-45cd-ba20-4aece2f69aea@app.fastmail.com>
Date: Fri, 7 Feb 2025 08:15:21 +0100
Message-ID: <CAHXoPRtLys1PG_bkkcOnSKU3JSTgBk=fDzY=+8qmq+_Jg3gqdg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Pipe Operator (again)
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000f5f405062d881f57"
From: oladoyinbov@gmail.com (Oladoyinbo Vincent)

--000000000000f5f405062d881f57
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

PHP codebase in general is quite unreadable due to robust way of doing
things. Pipe operator might make things more complicated even more...

But after reading the RFC, something came to my mind, a way to simplify
this stuff

What if we implement it this way:

```php

$pipe =3D " hello world "
           |> strtoupper(self)
           |> trim(self, ' ')
           |> htmlentities(self)
           |> fn (self): string =3D> ....

```

Maybe 'self' or '$this' can be used as the keyword param.

It's a suggestion anyways.

On Fri, 7 Feb 2025, 5:58=E2=80=AFam Larry Garfield, <larry@garfieldtech.com=
> wrote:

> Hi folks.  A few years ago I posted an RFC for a pipe operator, as seen i=
n
> many other languages.  At the time it didn't pass, in no small part becau=
se
> the implementation was a bit shaky and it was right before freeze.
> Nonetheless, there are now even more (bad) user-space implementations in
> the wild, as it gets brought up frequently in "what do you want in PHP?"
> threads (though nowhere near generics or better async, of course), so it
> seems clear there is demand in the market for it.
>
> It is now back with a better implementation (many thanks to Ilija for his
> help and guidance in that), and it's nowhere close to freeze, so here we =
go
> again:
>
> https://wiki.php.net/rfc/pipe-operator-v3
>
> Of particular note, since the last RFC I have concluded that a compose
> operator is a necessary complement to a pipe operator.  However, it's als=
o
> 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
> RFCs!", here's a small RFC. :-)
>
> --
>   Larry Garfield
>   larry@garfieldtech.com
>

--000000000000f5f405062d881f57
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">PHP codebase in general is quite unreadable due to robust=
 way of doing things. Pipe operator might make things more complicated even=
 more...<div dir=3D"auto"><br></div><div dir=3D"auto">But after reading the=
 RFC, something came to my mind, a way to simplify this stuff=C2=A0</div><d=
iv dir=3D"auto"><br></div><div dir=3D"auto">What if we implement it this wa=
y:</div><div dir=3D"auto"><br></div><div dir=3D"auto">```php</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">$pipe =3D &quot; hello world &quot;</=
div><div dir=3D"auto">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|&gt; strtou=
pper(self)</div><div dir=3D"auto">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
|&gt; trim(self, &#39; &#39;)</div><div dir=3D"auto">=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0|&gt; htmlentities(self)</div><div dir=3D"auto">=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|&gt; fn (self): string =3D&gt; ....</div=
><div dir=3D"auto"><br></div><div dir=3D"auto">```</div><div dir=3D"auto"><=
br></div><div dir=3D"auto">Maybe &#39;self&#39; or &#39;$this&#39; can be u=
sed as the keyword param.</div><div dir=3D"auto"><br></div><div dir=3D"auto=
">It&#39;s a suggestion anyways.</div></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Fri, 7 Feb 2025, 5:58=E2=80=AFam L=
arry Garfield, &lt;<a href=3D"mailto:larry@garfieldtech.com">larry@garfield=
tech.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi folks.=
=C2=A0 A few years ago I posted an RFC for a pipe operator, as seen in many=
 other languages.=C2=A0 At the time it didn&#39;t pass, in no small part be=
cause the implementation was a bit shaky and it was right before freeze.=C2=
=A0 Nonetheless, there are now even more (bad) user-space implementations i=
n the wild, as it gets brought up frequently in &quot;what do you want in P=
HP?&quot; threads (though nowhere near generics or better async, of course)=
, so it seems clear there is demand in the market for it.<br>
<br>
It is now back with a better implementation (many thanks to Ilija for his h=
elp and guidance in that), and it&#39;s nowhere close to freeze, so here we=
 go again:<br>
<br>
<a href=3D"https://wiki.php.net/rfc/pipe-operator-v3" rel=3D"noreferrer nor=
eferrer" target=3D"_blank">https://wiki.php.net/rfc/pipe-operator-v3</a><br=
>
<br>
Of particular note, since the last RFC I have concluded that a compose oper=
ator is a necessary complement to a pipe operator.=C2=A0 However, it&#39;s =
also going to be notably more work, and the two operators don&#39;t actuall=
y interact at all at the code level, so since people keep saying &quot;Smal=
l RFCs!&quot;, here&#39;s a small RFC. :-)<br>
<br>
-- <br>
=C2=A0 Larry Garfield<br>
=C2=A0 <a href=3D"mailto:larry@garfieldtech.com" target=3D"_blank" rel=3D"n=
oreferrer">larry@garfieldtech.com</a><br>
</blockquote></div>

--000000000000f5f405062d881f57--