Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126575
Content-Type: multipart/alternative;
 boundary="----sinikael-?=_1-17411706523220.6580496559372415"
Message-ID: <1741169717342.25808380.3585735442@gmail.com>
To: Eugene Sidelnyk <zsidelnik@gmail.com>
Cc: php internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] PHP True Async RFC
Date: Wed, 05 Mar 2025 10:30:52 +0000
In-Reply-To:
 <CAM0CcxhgOCsy46gp1qd4Zrdw8v0TfTkTTMin5EiHW18EDZRzwg@mail.gmail.com>
References:
 <CAM0CcxhgOCsy46gp1qd4Zrdw8v0TfTkTTMin5EiHW18EDZRzwg@mail.gmail.com>
User-Agent: Vivaldi Mail/7.1.3570.50
Precedence: bulk
MIME-Version: 1.0
From: edmond.ht@gmail.com (Edmond Dantes)

------sinikael-?=_1-17411706523220.6580496559372415
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hello, Eugene!





What I think it could be.


async function baz(): int {
   $foo = foo();
   $bar = bar();


   return $foo + $bar;
}


// value is returned just like from any other ordinary function
$val = baz(); 





If we have code like $x + $y, and in one block it follows rule 1 while in 
another block it follows rule 2, this increases the complexity of the 
language. The worst part is that the same operators exhibit DIFFERENT 
behavior in different contexts. This violates semantic integrity. (A 
similar issue occurred in C++ with operator overloading, where a 
theoretically elegant solution turned out to be terrible in practice).

If you want to achieve a clean syntax for concurrency in PHP, I would 
suggest considering pipes in the long run.

For example:

|> $users = getUsers() ||| $orders = getOrders()
|> mergeByColumn($users, $orders, 'orders')

-- 

Ed.
------sinikael-?=_1-17411706523220.6580496559372415
Content-Type: text/html; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

<html><head></head><body><span class="viv-signature"></span>Hello, 
Eugene!<br><blockquote style="margin: 0 0 0.80ex; border-left: #0000FF 2px 
solid; padding-left: 1ex"><div dir="auto"><div 
dir="auto"></div></div></blockquote><br><blockquote style="margin: 0 0 
0.80ex; border-left: #0000FF 2px solid; padding-left: 1ex"><div 
dir="auto"><div dir="auto"><br></div><div dir="auto">What I think it could 
be.</div><div dir="auto"><br></div><div dir="auto">async function baz(): 
int {</div><div dir="auto">&nbsp; $foo = foo();</div><div dir="auto">&nbsp; 
$bar = bar();</div><div dir="auto"><br></div><div dir="auto">&nbsp; return 
$foo + $bar;</div><div dir="auto">}</div><div dir="auto"><br></div><div 
dir="auto">// value is returned just like from any other ordinary 
function</div><div dir="auto">$val = baz();&nbsp;</div><div 
dir="auto"><br></div></div>
</blockquote><span class="viv-signature-below"><div><span 
class="viv-signature-below"><br></span></div><div><p data-end="420" 
data-start="0">If we have code like <code data-end="30" data-start="21">$x 
+ $y</code>, and in one block it follows rule 1 while in another block it 
follows rule 2, this increases the complexity of the language. The worst 
part is that the same operators exhibit DIFFERENT behavior in different 
contexts. This violates semantic integrity. (A similar issue occurred in 
C++ with operator overloading, where a theoretically elegant solution 
turned out to be terrible in practice).</p><p data-end="534" 
data-start="422">If you want to achieve a clean syntax for concurrency in 
PHP, I would suggest considering pipes in the long run.</p><p 
data-end="548" data-start="536">For example:</p><p data-end="548" 
data-start="536">|&gt; $users = getUsers() |||&nbsp;$orders = 
getOrders()<br>|&gt; mergeByColumn($users, $orders, 'orders')</p><p 
data-end="548" data-start="536"><span style="background-color: 
var(--colorBgIntense); color: 
var(--colorFgIntense);">--&nbsp;</span></p></div>Ed.</span></body></html>
------sinikael-?=_1-17411706523220.6580496559372415--