Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126627
Feedback-ID: id5114917:Fastmail
Message-ID: <be7cb263-93a1-4bd8-9416-ae4d3e0bafe6@rwec.co.uk>
Date: Fri, 7 Mar 2025 23:21:12 +0000
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] PHP True Async RFC
To: internals@lists.php.net
References: <CAMW7n8AJckEDzhGv9BdjNhq8zAdCqb4HsVr56vGi+izw50X6Dg@mail.gmail.com>
 <9964db8c-0ffe-43d5-8246-47fc76b07180@app.fastmail.com>
 <CAMW7n8CM7oBfXCDsKtV4hTFs40UmLCU3183WjYE2exLNqKDWLQ@mail.gmail.com>
 <78a03dd0-fd4a-4f4a-ad8a-37e5704f06fc@app.fastmail.com>
 <CAMW7n8C-Z18MKhyDX2+ofg70cRbwWOk=YWDAZpKtfLZsFVVRng@mail.gmail.com>
 <bb7a9f8f-0422-45e5-b4fc-f5757add92b4@app.fastmail.com>
 <CAMW7n8BnzL7d0bd_Y_jGOmyWegKQpm-FzrVFRCcDe=bNFZpi+A@mail.gmail.com>
 <08c8ad0b-e8f4-46e3-99f0-b80748d40b89@app.fastmail.com>
 <07973EAE-2D83-47A8-8FA0-84286C77C02B@rwec.co.uk>
 <48d66433-3ae9-4895-8361-7c81a0a3670d@app.fastmail.com>
Content-Language: en-GB
In-Reply-To: <48d66433-3ae9-4895-8361-7c81a0a3670d@app.fastmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: imsop.php@rwec.co.uk ("Rowan Tommins [IMSoP]")

On 07/03/2025 22:01, Larry Garfield wrote:
> Is that what you're suggesting?  If so, I'd have to think it through a bit more to see what guarantees that does[n't] provide.  It might work.  (I deliberately used spawn instead of "await" to avoid the mental association with JS async/await.)  My biggest issue is that this is starting to feel like colored functions, even if partially transparent.


Yes, that's pretty much what was in my head. I freely admit I haven't 
thought through the implications either.


> My biggest issue is that this is starting to feel like colored functions, even if partially transparent.


I think it's significantly *less* like coloured functions than passing 
around a nursery object. You could almost take this:

async function foo($bar int, $baz string) {
     spawn something_else();
}
spawn foo(42, 'hello');

As sugar for this:

function foo($bar int, $baz string, AsyncNursery $__nursery) {
     $__nursery->spawn( something_else(...) );
}
$__nursery->spawn( fn($n) => foo(42, 'hello', $n) );

However you spell it, you've had to change the function's *signature* in 
order to use async facilities in its *body*.


If the body can say "get current nursery", it can be called even if its 
*immediate* caller has no knowledge of async code, as long as we have 
some reasonable definition of "current".


-- 
Rowan Tommins
[IMSoP]