Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126515
Message-ID: <e8e159a0-8d3b-4e15-92bb-111d64191440@bastelstu.be>
Date: Wed, 26 Feb 2025 21:01:28 +0100
Precedence: bulk
MIME-Version: 1.0
Subject: Re: [PHP-DEV] [RFC] Pipe Operator (again)
To: internals@lists.php.net
References: <de8140ab-0941-45cd-ba20-4aece2f69aea@app.fastmail.com>
 <5a584219f120385e7e30f6d0a46cc108@bastelstu.be>
 <bd93bbb9-e970-4211-af59-4ccd643dc52f@app.fastmail.com>
 <1b8840b9-5ae0-40db-8af2-521ac5888c7c@bastelstu.be>
Content-Language: en-US
In-Reply-To: <1b8840b9-5ae0-40db-8af2-521ac5888c7c@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

On 2/8/25 12:36, Tim Düsterhus wrote:
>> If the expression on the right side that produces a Closure has side effects (output, DB interaction, etc.), then the order in which those side effects happen may change with the different restructuring.
> 
> That is a good point. I see you added a precedence section, but this
> does not fully explain the order of operations in face of side-effects
> and more generally with regard to “short-circuiting” behavior. An OPcode
> dump would explain that.
> 
> Specifically for:
> 
>       function foo()     { echo __FUNCTION__, PHP_EOL; return 1; }
>       function bar()     { echo __FUNCTION__, PHP_EOL; return false; }
>       function baz($in)  { echo __FUNCTION__, PHP_EOL; return $in; }
>       function quux($in) { echo __FUNCTION__, PHP_EOL; return $in; }
> 
>       foo()
>           |> (bar() ? baz(...) : quux(...))
>           |> var_dump(...);
> 
> What will the output be?

This is unresolved.

Best regards
Tim Düsterhus