Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127344
Precedence: bulk
MIME-Version: 1.0
References: <c77374f9-d638-418e-8151-d4fdfbbd4561@app.fastmail.com>
In-Reply-To: <c77374f9-d638-418e-8151-d4fdfbbd4561@app.fastmail.com>
Date: Tue, 13 May 2025 12:41:18 -0600
Message-ID: <CAFMT4NrV0AvMpbgUE-X9Qcr+Q-4WzsB6=Z3YwhwPgdGnqqUG+Q@mail.gmail.com>
Subject: Re: [PHP-DEV] [Vote] Pipe operator
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: levim@php.net (Levi Morrison)

On Mon, May 12, 2025 at 8:00=E2=80=AFPM Larry Garfield <larry@garfieldtech.=
com> wrote:
>
> I hereby open the vote on the Pipe operator RFC:
>
> https://wiki.php.net/rfc/pipe-operator-v3
>
> The vote will run until 26 May.

Hey, Larry, quick check:

> Supporting pass-by-ref parameters in simple cases is quite easy, and
> a naive implementation would support it. However, passing a value
> from a compound value (an object property or array element) by
> reference does not work, and throws an =E2=80=9CArgument could not be pas=
sed
> by reference=E2=80=9D error. In practice, it is easier to forbid pass-by-=
ref
> parameters in pipe than to allow them.

Is this a restriction that can be lifted in a future version? I agree
that it's unlikely to be useful, but if the `$temp =3D` chain version
supports it, then so too I would expect a pipeline to be able to
handle it.