Re: PHP True Async RFC - Stage 2

From: Date: Thu, 20 Mar 2025 17:54:12 +0000
Subject: Re: PHP True Async RFC - Stage 2
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
On Thu, Mar 20, 2025, at 2:06 AM, Edmond Dantes wrote:
> This is simply a wonderful explanation. I will be able to go through each point.
>
> But before that, let's recall what spawn essentially is.  
> Spawn is an operation that creates a separate execution context and 
> then calls a function within it.  
> To perform this, spawn requires two things:
> 1. **callable** – something that can be called; this is an expression 
> or the result of an expression.  
> 2. **argument list** – a list of arguments.  

Nitpick to make sure we're talking about the same thing: What does "Separate execution
context" mean here?  Because a keyword whose description includes "and" is always a
yellow flag at least.  (See also: readonly.)  One thing should not do two things.  Unless what you
mean here is it creates a logical coroutine, within the current async scope.

(I suspect this level of nitpickiness is where the confusion between us lies.)

--Larry Garfield


Thread (59 messages)

« previous php.internals (#126874) next »