Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126830
Precedence: bulk
MIME-Version: 1.0
References: <CAMW7n8DQqUhnb+U+WcA7bJ-APRDTtzuJC4m8s-q_2LH7bEuH+A@mail.gmail.com>
 <fdeeec46-55c0-409e-a230-f04c3af23464@app.fastmail.com>
In-Reply-To: <fdeeec46-55c0-409e-a230-f04c3af23464@app.fastmail.com>
Date: Tue, 18 Mar 2025 23:36:35 +0200
Message-ID: <CAMW7n8DUq0VzGGwL5fWW_Th0c-=gbChkNL0cOFxSRxSvG252zA@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async RFC - Stage 2
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a146ca0630a4b3f2"
From: edmond.ht@gmail.com (Edmond Dantes)

--000000000000a146ca0630a4b3f2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Continuing the discussion from [[PHP-DEV] PHP True Async RFC - Stage 2](
https://discourse.thephp.foundation/t/php-dev-php-true-async-rfc-stage-2/15=
73/16
):

[quote=3D"Crell, post:16, topic:1573"]
// Creates an async scope, in which you can create coroutines.
[/quote]

Yes, I understand what this is about.
Here=E2=80=99s a more specific example: launching two coroutines and waitin=
g for
both.

```php
$scope =3D new Scope();
$scope->spawn(fn() =3D> ...);
$scope->spawn(fn() =3D> ...);

await $scope;
```

The downside of this code is that the programmer might forget to write
`await $scope`.
Additionally, they constantly need to write `$scope->`.

This code can be replaced with syntactic sugar:

```
async {
    spawn ...
    spawn ...
};
```

Am I understanding this correctly? Does it look nice? I think yes.
And at the same time, if the closing bracket is missing, the compiler will
throw an error, meaning you can't forget to `await`.

That is the only advantage of this approach.

Now, let's talk about the downsides.

```
function task(): void {
    spawn function() {
        echo "What?";
    };

    async {
        spawn ...
        spawn ...
    };
}

```

Let me explain.
You can write the `spawn` operator **outside** the `async` block. Why?

Because **nothing** can prevent you from doing so. It=E2=80=99s simply impo=
ssible.
After all, the function might already be executing inside another `async`
block outside its scope.

That=E2=80=99s exactly what happens an `async` block is essentially always =
present
as soon as `index.php` starts running.

It is necessary to determine whether this syntax truly provides enough
benefits compared to the direct implementation.

I will think about it.

--000000000000a146ca0630a4b3f2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Continuing the discussion from [[PHP-DEV] PHP True Async R=
FC - Stage 2](<a href=3D"https://discourse.thephp.foundation/t/php-dev-php-=
true-async-rfc-stage-2/1573/16">https://discourse.thephp.foundation/t/php-d=
ev-php-true-async-rfc-stage-2/1573/16</a>):<br><br>[quote=3D&quot;Crell, po=
st:16, topic:1573&quot;]<br>// Creates an async scope, in which you can cre=
ate coroutines.<br>[/quote]<br><br>Yes, I understand what this is about. =
=C2=A0<br>Here=E2=80=99s a more specific example: launching two coroutines =
and waiting for both.<br><br>```php<br>$scope =3D new Scope();<br>$scope-&g=
t;spawn(fn() =3D&gt; ...);<br>$scope-&gt;spawn(fn() =3D&gt; ...);<br><br>aw=
ait $scope;<br>```<br><br>The downside of this code is that the programmer =
might forget to write `await $scope`.<br>Additionally, they constantly need=
 to write `$scope-&gt;`.<br><br>This code can be replaced with syntactic su=
gar:<br><br>```<br>async {<br>=C2=A0 =C2=A0 spawn ...<br>=C2=A0 =C2=A0 spaw=
n ...<br>};<br>```<br><br>Am I understanding this correctly? Does it look n=
ice? I think yes.<br>And at the same time, if the closing bracket is missin=
g, the compiler will throw an error, meaning you can&#39;t forget to `await=
`.<br><br>That is the only advantage of this approach.<br><br>Now, let&#39;=
s talk about the downsides.<br><br>```<br>function task(): void {<br>=C2=A0=
 =C2=A0 spawn function() {<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 echo &quot;What?&=
quot;;<br>=C2=A0 =C2=A0 };<br><br>=C2=A0 =C2=A0 async {<br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 spawn ...<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 spawn ...<br>=C2=A0 =
=C2=A0 };<br>}<br><br>```<br><br>Let me explain.<br>You can write the `spaw=
n` operator **outside** the `async` block. Why?<br><br>Because **nothing** =
can prevent you from doing so. It=E2=80=99s simply impossible.<br>After all=
, the function might already be executing inside another `async` block outs=
ide its scope.<br><br>That=E2=80=99s exactly what happens an `async` block =
is essentially always present as soon as `index.php` starts running.<br><br=
>It is necessary to determine whether this syntax truly provides enough ben=
efits compared to the direct implementation.<br><br>I will think about it.=
=C2=A0=C2=A0<br></div>

--000000000000a146ca0630a4b3f2--