Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126366
Precedence: bulk
MIME-Version: 1.0
Date: Mon, 10 Feb 2025 11:04:32 +0100
To: internals@lists.php.net
Subject: Re: [PHP-DEV] [RFC] Pipe Operator (again)
In-Reply-To: <de8140ab-0941-45cd-ba20-4aece2f69aea@app.fastmail.com>
References: <de8140ab-0941-45cd-ba20-4aece2f69aea@app.fastmail.com>
Message-ID: <e73d708badfb33bd7b120d4be6d95c04@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

Am 2025-02-07 05:57, schrieb Larry Garfield:
> https://wiki.php.net/rfc/pipe-operator-v3

After also having taken a look at the implementation and then the 
updated “Precedence” section, I'd like to argue in favor of moving `|>` 
to have a higher precedence than the comparison operators (i.e. between 
string concatenation and `<`). This would mean that `|>` has higher 
precedence than `??`, but looking at the following examples, that 
appears to be the more useful default anyways.

I'm rather interested in handling a `null` pipe result:

     $user = $request->get('id')
         |> $database->fetchUser(...)
         ?? new GuestUser();

Than handling a null callback (using the RFC example, because I can't 
even think of a real-world use-case):

     $res1 = 5
         |> $null_func ?? defaultFunc(...);

To give some more examples of what would be possible without parentheses 
then:

     $containsNotOnlyZero = $someString
         |> fn ($str) => str_replace('0', '', $str)
         |> strlen(...)
         > 0;

Which is not particularly pretty, but appears to be more useful than 
either passing a boolean into a single-argument function or piping into 
a boolean (which would error).

Best regards
Tim Düsterhus