Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126711
To: internals@lists.php.net
Subject: Re: [PHP-DEV] [RFC] Pipe Operator (again)
Date: Tue, 11 Mar 2025 10:00:52 +0100
Message-ID: <5931820.DvuYhMxLoT@come-prox15amd>
In-Reply-To: <38b57201-5091-4c68-988b-9ce3beac8fcb@cubiclesoft.com>
References:
 <de8140ab-0941-45cd-ba20-4aece2f69aea@app.fastmail.com>
 <38b57201-5091-4c68-988b-9ce3beac8fcb@cubiclesoft.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart6200254.lOV4Wx5bFT";
 micalg="pgp-sha512"; protocol="application/pgp-signature"
From: come@chilliet.eu (=?UTF-8?B?Q8O0bWU=?= Chilliet)

--nextPart6200254.lOV4Wx5bFT
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: =?UTF-8?B?Q8O0bWU=?= Chilliet <come@chilliet.eu>
To: internals@lists.php.net
Subject: Re: [PHP-DEV] [RFC] Pipe Operator (again)
Date: Tue, 11 Mar 2025 10:00:52 +0100
Message-ID: <5931820.DvuYhMxLoT@come-prox15amd>
In-Reply-To: <38b57201-5091-4c68-988b-9ce3beac8fcb@cubiclesoft.com>
MIME-Version: 1.0

Hello,

I=E2=80=99m also wondering when I see code examples in the RFC like:

$profit =3D [1, 4, 5]=20
    |> loadMany(...)
    |> fn(array $records) =3D> array_map(makeWidget(...), $records)
    |> fn(array $ws) =3D> array_filter(isOnSale(...), $ws)
    |> fn(array $ws) =3D> array_map(sellWidget(...), $ws)
    |> array_sum(...);

This would be way better on performances as a single foreach, no?
I feel like this pipe operator encourages coders to use array_* functions w=
ith closures, which is often terrible performances compared to a loop.

How would the performance of the above compare with:

$profit =3D 0;
foreach (loadMany($input) as $item) {
  $widget =3D makeWidget($item);
  if (!isOnSale($widget)) {
    continue;
  }
  $profit +=3D sellWidget($widget);
}

C=C3=B4me
--nextPart6200254.lOV4Wx5bFT
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEE8x20ac73tsA2u7cuwRZWc8b9+7kFAmfP+8QACgkQwRZWc8b9
+7lZwAf9G6qz5LnIxw9UyDoZev1NC0DDPwWsNVY3tyDVpVGFau/kTD/eTHbisF16
kUzqpdgCNBqRbueziTlniWV7Zz/vXN62cbtyTBcU5WSd01paqXEupOzCFpzQLHrP
KynIm/MUrf6D0Z6fhZwbYsoinfKAYxCn7Mt7ul01JIpEBqGc7AFD9THCHBASDrvP
UOPIXg3lfVZWyBFIaWaJ07l7eaHfLZDhXx6xudVh9gBxX9Pn8Xu1A8Iv+n5gcusk
VgXGEUDqzDXpiE1kexzcX/oBUdvb7VHaDXVeKM6c+dDesQvt4VrCXqwleBOzCffB
mWDPMC2wT+NX8F+dKuGKSAhbd6iHFg==
=aSvM
-----END PGP SIGNATURE-----

--nextPart6200254.lOV4Wx5bFT--