Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126884
Precedence: bulk
MIME-Version: 1.0
References: <CAMW7n8DQqUhnb+U+WcA7bJ-APRDTtzuJC4m8s-q_2LH7bEuH+A@mail.gmail.com>
In-Reply-To: <CAMW7n8DQqUhnb+U+WcA7bJ-APRDTtzuJC4m8s-q_2LH7bEuH+A@mail.gmail.com>
Date: Fri, 21 Mar 2025 12:03:50 +0200
Message-ID: <CAMW7n8BTCzYxmOBpjkCW-pis29O=WLhbL-oM1VMo-gDNTm7xeQ@mail.gmail.com>
Subject: [PHP-DEV] Re: PHP True Async RFC - Stage 2
To: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000923da50630d75f3f"
From: edmond.ht@gmail.com (Edmond Dantes)

--000000000000923da50630d75f3f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Good day, everyone.

As I write more code examples, I'm starting to get annoyed by the verbosity
of the `spawn in $scope` construct=E2=80=94especially in situations where a=
ll
spawns need to happen within the same context.

At the same time, in 80% of cases, it turns out that explicitly defining
`$scope` is the only correct approach to avoid shooting yourself in the
foot.
So, it turns out that the `spawn in $scope` construct is used far more
frequently than a plain `spawn`.

I remembered an example that Larry came up with and decided to use it as
syntactic sugar.

There=E2=80=99s some doubt because the actual gain in characters is minimal=
. This
block doesn't change the logic in any way.
The convenience lies in the fact that within the block, it=E2=80=99s clear =
which
`$scope` is currently active.
However, this is more about visual organization than logical structure.

Here's what I ended up with:

### Async blocks

Consider the following code:

```php
function generateReport(): void
{
    $scope =3D Scope::inherit();

    try {
        [$employees, $salaries, $workHours] =3D await Async\all([
            spawn in $scope fetchEmployees(),
            spawn in $scope fetchSalaries(),
            spawn in $scope fetchWorkHours()
        ]);

        foreach ($employees as $id =3D> $employee) {
            $salary =3D $salaries[$id] ?? 'N/A';
            $hours =3D $workHours[$id] ?? 'N/A';
            echo "{$employee['name']}: salary =3D $salary, hours =3D $hours=
\n";
        }

    } catch (Exception $e) {
        echo "Failed to generate report: ", $e->getMessage(), "\n";
    }
}
```

with async

```php
function generateReport(): void
{
    try {

        $scope =3D Scope::inherit();

        async $scope {
            [$employees, $salaries, $workHours] =3D await Async\all([
                spawn fetchEmployees(),
                spawn fetchSalaries(),
                spawn fetchWorkHours()
            ]);

            foreach ($employees as $id =3D> $employee) {
                $salary =3D $salaries[$id] ?? 'N/A';
                $hours =3D $workHours[$id] ?? 'N/A';
                echo "{$employee['name']}: salary =3D $salary, hours =3D
$hours\n";
            }
        }

    } catch (Exception $e) {
        echo "Failed to generate report: ", $e->getMessage(), "\n";
    }
}

```

#### async syntax

```php
async <scope> {
    <codeBlock>
}
```

--000000000000923da50630d75f3f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Good day, everyone.=C2=A0=C2=A0</div><div><br></div><=
div>As I write more code examples, I&#39;m starting to get annoyed by the v=
erbosity of the `spawn in $scope` construct=E2=80=94especially in situation=
s where all spawns need to happen within the same context.<br><br>At the sa=
me time, in 80% of cases, it turns out that explicitly defining `$scope` is=
 the only correct approach to avoid shooting yourself in the foot. =C2=A0<b=
r>So, it turns out that the `spawn in $scope` construct is used far more fr=
equently than a plain `spawn`.<br><br>I remembered an example that Larry ca=
me up with and decided to use it as syntactic sugar. =C2=A0</div><div><br><=
/div><div>There=E2=80=99s some doubt because the actual gain in characters =
is minimal. This block doesn&#39;t change the logic in any way. =C2=A0<br>T=
he convenience lies in the fact that within the block, it=E2=80=99s clear w=
hich `$scope` is currently active. =C2=A0<br>However, this is more about vi=
sual organization than logical structure.<br><br></div><div>Here&#39;s what=
 I ended up with:<br></div><div><br></div><div>### Async blocks<br><br>Cons=
ider the following code:<br><br>```php<br>function generateReport(): void<b=
r>{<br>=C2=A0 =C2=A0 $scope =3D Scope::inherit();<br><br>=C2=A0 =C2=A0 try =
{<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 [$employees, $salaries, $workHours] =3D aw=
ait Async\all([<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 spawn in $scop=
e fetchEmployees(),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 spawn in $=
scope fetchSalaries(),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 spawn i=
n $scope fetchWorkHours()<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 ]);<br><br>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 foreach ($employees as $id =3D&gt; $employee) {<br>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 $salary =3D $salaries[$id] ?? &#39;N=
/A&#39;;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 $hours =3D $workHours=
[$id] ?? &#39;N/A&#39;;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 echo &=
quot;{$employee[&#39;name&#39;]}: salary =3D $salary, hours =3D $hours\n&qu=
ot;;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 }<br><br>=C2=A0 =C2=A0 } catch (Excepti=
on $e) {<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 echo &quot;Failed to generate repor=
t: &quot;, $e-&gt;getMessage(), &quot;\n&quot;;<br>=C2=A0 =C2=A0 }<br>}<br>=
```<br><br>with async<br><br>```php<br>function generateReport(): void<br>{=
<br>=C2=A0 =C2=A0 try {<br>=C2=A0 =C2=A0 <br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 $s=
cope =3D Scope::inherit();<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <br>=C2=A0 =C2=A0=
 =C2=A0 =C2=A0 async $scope {<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
[$employees, $salaries, $workHours] =3D await Async\all([<br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 spawn fetchEmployees(),<br>=C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 spawn fetchSalaries(),<br=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 spawn fetchWorkHou=
rs()<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ]);<br>=C2=A0 =C2=A0 <br>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 foreach ($employees as $id =3D&gt=
; $employee) {<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 $=
salary =3D $salaries[$id] ?? &#39;N/A&#39;;<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 $hours =3D $workHours[$id] ?? &#39;N/A&#39;;<br=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 echo &quot;{$emplo=
yee[&#39;name&#39;]}: salary =3D $salary, hours =3D $hours\n&quot;;<br>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 } =C2=A0 =C2=A0 =C2=A0 =C2=A0<br>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 }<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 <br>=C2=A0 =C2=A0=
 } catch (Exception $e) {<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 echo &quot;Failed =
to generate report: &quot;, $e-&gt;getMessage(), &quot;\n&quot;;<br>=C2=A0 =
=C2=A0 }<br>}<br><br>```<br><br>#### async syntax<br><br>```php<br>async &l=
t;scope&gt; {<br>=C2=A0 =C2=A0 &lt;codeBlock&gt;<br>}<br>```<br></div><div>=
<br></div></div>

--000000000000923da50630d75f3f--