Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126320
Precedence: bulk
MIME-Version: 1.0
References: <de8140ab-0941-45cd-ba20-4aece2f69aea@app.fastmail.com> <CAHXoPRtLys1PG_bkkcOnSKU3JSTgBk=fDzY=+8qmq+_Jg3gqdg@mail.gmail.com>
In-Reply-To: <CAHXoPRtLys1PG_bkkcOnSKU3JSTgBk=fDzY=+8qmq+_Jg3gqdg@mail.gmail.com>
Date: Fri, 7 Feb 2025 09:36:50 +0200
Message-ID: <CAM0CcxikuzA6GXuWYnLfR51Dsvq_o8_LPGbS5Uf8sPvusao9HA@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Pipe Operator (again)
To: Oladoyinbo Vincent <oladoyinbov@gmail.com>
Cc: Larry Garfield <larry@garfieldtech.com>, php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a3606d062d886cb9"
From: zsidelnik@gmail.com (Eugene Sidelnyk)

--000000000000a3606d062d886cb9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi, Larry, That's super! I hope it will pass!

Oladoyinbo, IMO the way it is described right now (e.g. explicit closures)
is much more elegant than a new way of doing things that's not so obvious
and will be necessary to keep in mind and support anyway.

If it'd be necessary to simplify the stuff, like passing particular
parameter from the input pipe into the function at the particular position,
- I think it would be possible to do it with partial function application I
hope to see in the future. (e.g. bind callback for array_map function,
making a new function for the pipe that will accept the only parameter -
input array)

Thank you

On Fri, Feb 7, 2025, 9:16 AM Oladoyinbo Vincent <oladoyinbov@gmail.com>
wrote:

> 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.c=
om>
> wrote:
>
>> Hi folks.  A few years ago I posted an RFC for a pipe operator, as seen
>> in many other languages.  At the time it didn't pass, in no small part
>> because the implementation was a bit shaky and it was right before freez=
e.
>> 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 hi=
s
>> 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 al=
so
>> 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
>>
>

--000000000000a3606d062d886cb9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Hi, Larry, That&#39;s super! I hope it will pass!</p>
<p dir=3D"ltr">Oladoyinbo, IMO the way it is described right now (e.g. expl=
icit closures) is much more elegant than a new way of doing things that&#39=
;s not so obvious and will be necessary to keep in mind and support anyway.=
 </p>
<p dir=3D"ltr">If it&#39;d be necessary to simplify the stuff, like passing=
 particular parameter from the input pipe into the function at the particul=
ar position, - I think it would be possible to do it with partial function =
application I hope to see in the future. (e.g. bind callback for array_map =
function, making a new function for the pipe that will accept the only para=
meter - input array)</p>
<p dir=3D"ltr">Thank you </p>
<br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=
=3D"gmail_attr">On Fri, Feb 7, 2025, 9:16 AM Oladoyinbo Vincent &lt;<a href=
=3D"mailto:oladoyinbov@gmail.com">oladoyinbov@gmail.com</a>&gt; wrote:<br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><div dir=3D"auto">PHP codebase in gener=
al is quite unreadable due to robust way of doing things. Pipe operator mig=
ht make things more complicated even more...<div dir=3D"auto"><br></div><di=
v dir=3D"auto">But after reading the RFC, something came to my mind, a way =
to simplify this stuff=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"a=
uto">What if we implement it this way:</div><div dir=3D"auto"><br></div><di=
v dir=3D"auto">```php</div><div dir=3D"auto"><br></div><div dir=3D"auto">$p=
ipe =3D &quot; hello world &quot;</div><div dir=3D"auto">=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0|&gt; strtoupper(self)</div><div dir=3D"auto">=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|&gt; trim(self, &#39; &#39;)</div><d=
iv 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 used as the keyword param.</div><div d=
ir=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 Larry Garfield, &lt;<a href=3D"mailto:=
larry@garfieldtech.com" target=3D"_blank" rel=3D"noreferrer">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 noreferrer" target=3D"_blank">https://wiki.php.net/rfc/pipe-operato=
r-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" rel=3D"noreferrer noreferr=
er" target=3D"_blank">larry@garfieldtech.com</a><br>
</blockquote></div>
</blockquote></div>

--000000000000a3606d062d886cb9--