Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126345
Feedback-ID: ifab94697:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Sat, 08 Feb 2025 00:35:52 +0100
To: internals@lists.php.net
Message-ID: <3e01de2d-15b5-48a7-9322-3f92c38957cc@app.fastmail.com>
In-Reply-To: <c9b0a485-4bb5-40d3-9280-41f196e12a2e@app.fastmail.com>
References: <de8140ab-0941-45cd-ba20-4aece2f69aea@app.fastmail.com>
 <5a584219f120385e7e30f6d0a46cc108@bastelstu.be>
 <bd93bbb9-e970-4211-af59-4ccd643dc52f@app.fastmail.com>
 <040da4e2-2595-42ad-ab94-a0e87aed1a79@app.fastmail.com>
 <c9b0a485-4bb5-40d3-9280-41f196e12a2e@app.fastmail.com>
Subject: Re: [PHP-DEV] [RFC] Pipe Operator (again)
Content-Type: multipart/alternative;
 boundary=d189cec4ea4e4d71ae4ef52a65243dd5
From: rob@bottled.codes ("Rob Landers")

--d189cec4ea4e4d71ae4ef52a65243dd5
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On Sat, Feb 8, 2025, at 00:19, Larry Garfield wrote:
> On Fri, Feb 7, 2025, at 4:54 PM, Rob Landers wrote:
>=20
> > Put another way, what is the order of operations for this new operat=
or?
> >
> > For example, what is the output of
> >
> > $x ? $y |> strlen(=E2=80=A6) : $z
> >
> > $x + $y |> sqrt(=E2=80=A6) . EOL
> >
> > Etc.
> >
> > I noticed this seems to be missing from the RFC. As a new operator, =
I=20
> > think it should be important to specify that.=20
> >
> > =E2=80=94 Rob
>=20
> Pipe deliberately binds fairly low, so most other operators will happe=
n first.  Including +, ?? and ? :, for which there are tests:
>=20
> https://github.com/php/php-src/pull/17118/files#diff-81789df7e32480162=
6ef4ef8f629cc95dceed4c09073a2b58b70c811bf776904
>=20
> https://github.com/php/php-src/pull/17118/files#diff-56cbcf85bd7f68fa7=
a1f837eb15dcc536576986f366976f9642ad20867c471fd
>=20
> https://github.com/php/php-src/pull/17118/files#diff-775c14f54cd1a2771=
9d30bfab62024aeb1625bc3f3621fa0e7c16fb1c7957fdd
>=20
> So in the examples above, the second would add $x and $y first, then s=
quare-root the result.  The first, I think would probably need parens to=
 avoid being invalid but I'd have to try it to be sure.
>=20
> --Larry Garfield
>=20

It might be good to specify it in the RFC so if there are any strange be=
havior, decades from now, there will be an intent to figure out if it is=
 a feature or a bug.=20

As to the ternary, it is the difference between that example being valid=
 and this `$x |> $x > 3 ? foo(=E2=80=A6) : bar(...) |> baz(=E2=80=A6)` m=
aking sense or not. Personally, I wouldn=E2=80=99t write this code and w=
ould use parens to disambiguate, but it=E2=80=99d be handy to know when =
doing code reviews of authors who don=E2=80=99t.

=E2=80=94 Rob
--d189cec4ea4e4d71ae4ef52a65243dd5
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 Sat, Feb 8, 2025, at 00:19, Larry Garfield wrote:<br><=
/div><blockquote type=3D"cite" id=3D"qt" style=3D""><div>On Fri, Feb 7, =
2025, at 4:54 PM, Rob Landers wrote:<br></div><div><br></div><div>&gt; P=
ut another way, what is the order of operations for this new operator?<b=
r></div><div>&gt;<br></div><div>&gt; For example, what is the output of<=
br></div><div>&gt;<br></div><div>&gt; $x ? $y |&gt; strlen(=E2=80=A6) : =
$z<br></div><div>&gt;<br></div><div>&gt; $x + $y |&gt; sqrt(=E2=80=A6) .=
 EOL<br></div><div>&gt;<br></div><div>&gt; Etc.<br></div><div>&gt;<br></=
div><div>&gt; I noticed this seems to be missing from the RFC. As a new =
operator, I&nbsp;<br></div><div>&gt; think it should be important to spe=
cify that.&nbsp;<br></div><div>&gt;<br></div><div>&gt; =E2=80=94 Rob<br>=
</div><div><br></div><div>Pipe deliberately binds fairly low, so most ot=
her operators will happen first.&nbsp; Including +, ?? and ? :, for whic=
h there are tests:<br></div><div><br></div><div><a href=3D"https://githu=
b.com/php/php-src/pull/17118/files#diff-81789df7e324801626ef4ef8f629cc95=
dceed4c09073a2b58b70c811bf776904">https://github.com/php/php-src/pull/17=
118/files#diff-81789df7e324801626ef4ef8f629cc95dceed4c09073a2b58b70c811b=
f776904</a><br></div><div><br></div><div><a href=3D"https://github.com/p=
hp/php-src/pull/17118/files#diff-56cbcf85bd7f68fa7a1f837eb15dcc536576986=
f366976f9642ad20867c471fd">https://github.com/php/php-src/pull/17118/fil=
es#diff-56cbcf85bd7f68fa7a1f837eb15dcc536576986f366976f9642ad20867c471fd=
</a><br></div><div><br></div><div><a href=3D"https://github.com/php/php-=
src/pull/17118/files#diff-775c14f54cd1a27719d30bfab62024aeb1625bc3f3621f=
a0e7c16fb1c7957fdd">https://github.com/php/php-src/pull/17118/files#diff=
-775c14f54cd1a27719d30bfab62024aeb1625bc3f3621fa0e7c16fb1c7957fdd</a><br=
></div><div><br></div><div>So in the examples above, the second would ad=
d $x and $y first, then square-root the result.&nbsp; The first, I think=
 would probably need parens to avoid being invalid but I'd have to try i=
t to be sure.<br></div><div><br></div><div>--Larry Garfield<br></div><di=
v><br></div></blockquote><div><br></div><div>It might be good to specify=
 it in the RFC so if there are any strange behavior, decades from now, t=
here will be an intent to figure out if it is a feature or a bug.&nbsp;<=
br></div><div><br></div><div>As to the ternary, it is the difference bet=
ween that example being valid and this `$x |&gt; $x &gt; 3 ? foo(=E2=80=A6=
) : bar(...) |&gt; baz(=E2=80=A6)` making sense or not. Personally, I wo=
uldn=E2=80=99t write this code and would use parens to disambiguate, but=
 it=E2=80=99d be handy to know when doing code reviews of authors who do=
n=E2=80=99t.<br></div><div><br></div><div id=3D"sig121229152">=E2=80=94 =
Rob<br></div></body></html>
--d189cec4ea4e4d71ae4ef52a65243dd5--