Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126323
Feedback-ID: ifab94697:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Fri, 07 Feb 2025 09:14:47 +0100
To: internals@lists.php.net
Message-ID: <6f3bed6d-a537-456d-b90c-b5b864835998@app.fastmail.com>
In-Reply-To: <de8140ab-0941-45cd-ba20-4aece2f69aea@app.fastmail.com>
References: <de8140ab-0941-45cd-ba20-4aece2f69aea@app.fastmail.com>
Subject: Re: [PHP-DEV] [RFC] Pipe Operator (again)
Content-Type: multipart/alternative;
 boundary=4ed7bc629e9140d68133df679193c935
From: rob@bottled.codes ("Rob Landers")

--4ed7bc629e9140d68133df679193c935
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On Fri, Feb 7, 2025, at 05:57, Larry Garfield wrote:
> Hi folks.  A few years ago I posted an RFC for a pipe operator, as see=
n 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 free=
ze.  Nonetheless, there are now even more (bad) user-space implementatio=
ns 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.
>=20
> 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 her=
e we go again:
>=20
> https://wiki.php.net/rfc/pipe-operator-v3
>=20
> 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 a=
lso 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 RF=
Cs!", here's a small RFC. :-)
>=20
> --=20
>   Larry Garfield
>   larry@garfieldtech.com
>=20

Hey Larry,

Maybe I missed it, but what happens here?

[1,2] |> add(=E2=80=A6)

Is the array deconstructed or passed as-is? Further, if it is passed as-=
is (my gut is telling me it will be), then what is the error? Is it the =
normal =E2=80=9Cmissing second parameter when calling add()=E2=80=9D err=
or or a new error specific to pipes?

If it is passed as-is, would the following be legal?

=E2=80=A6[1,2] |> add(=E2=80=A6)

=E2=80=94 Rob
--4ed7bc629e9140d68133df679193c935
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div><br></div><div>=
<br></div><div>On Fri, Feb 7, 2025, at 05:57, Larry Garfield wrote:<br><=
/div><blockquote type=3D"cite" id=3D"qt" style=3D""><div>Hi folks.&nbsp;=
 A few years ago I posted an RFC for a pipe operator, as seen in many ot=
her languages.&nbsp; At the time it didn't pass, in no small part becaus=
e the implementation was a bit shaky and it was right before freeze.&nbs=
p; 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 P=
HP?" threads (though nowhere near generics or better async, of course), =
so it seems clear there is demand in the market for it.<br></div><div><b=
r></div><div>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 fre=
eze, so here we go again:<br></div><div><br></div><div><a href=3D"https:=
//wiki.php.net/rfc/pipe-operator-v3">https://wiki.php.net/rfc/pipe-opera=
tor-v3</a><br></div><div><br></div><div>Of particular note, since the la=
st RFC I have concluded that a compose operator is a necessary complemen=
t to a pipe operator.&nbsp; However, it's also going to be notably more =
work, and the two operators don't actually interact at all at the code l=
evel, so since people keep saying "Small RFCs!", here's a small RFC. :-)=
<br></div><div><br></div><div>--&nbsp;<br></div><div>&nbsp; Larry Garfie=
ld<br></div><div>&nbsp;&nbsp;<a href=3D"mailto:larry@garfieldtech.com">l=
arry@garfieldtech.com</a><br></div><div><br></div></blockquote><div><br>=
</div><div>Hey Larry,<br></div><div><br></div><div>Maybe I missed it, bu=
t what happens here?<br></div><div><br></div><div>[1,2] |&gt; add(=E2=80=
=A6)<br></div><div><br></div><div>Is the array deconstructed or passed a=
s-is? Further, if it is passed as-is (my gut is telling me it will be), =
then what is the error? Is it the normal =E2=80=9Cmissing second paramet=
er when calling add()=E2=80=9D error or a new error specific to pipes?</=
div><div><br></div><div>If it is passed as-is, would the following be le=
gal?<br></div><div><br></div><div>=E2=80=A6[1,2] |&gt; add(=E2=80=A6)</d=
iv><div><br></div><div id=3D"sig121229152">=E2=80=94 Rob<br></div></body=
></html>
--4ed7bc629e9140d68133df679193c935--