Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126637
Feedback-ID: ifab94697:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Sat, 08 Mar 2025 09:26:51 +0100
To: "Edmond Dantes" <edmond.ht@gmail.com>
Cc: internals@lists.php.net
Message-ID: <62505751-7d35-4ffd-ace2-cbf099ee2b8c@app.fastmail.com>
In-Reply-To: 
 <CAMW7n8BN6kNny3CRxKEtCWari5eQ0uCj42g2xQLjFqXCkyF=Rw@mail.gmail.com>
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>
 <be7cb263-93a1-4bd8-9416-ae4d3e0bafe6@rwec.co.uk>
 <dbce8889-016a-4c59-864c-d8fdec895adc@app.fastmail.com>
 <CAMW7n8BN6kNny3CRxKEtCWari5eQ0uCj42g2xQLjFqXCkyF=Rw@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async RFC
Content-Type: multipart/alternative;
 boundary=7bf96d7fa1cf41bc9a51865a5b055a31
From: rob@bottled.codes ("Rob Landers")

--7bf96d7fa1cf41bc9a51865a5b055a31
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On Sat, Mar 8, 2025, at 09:24, Edmond Dantes wrote:
> >=20
> >for($i =3D 0; $i < 10; $i++) $results[] =3D async\async(fn($f) =3D> f=
ile_get_contents($f),
> > $file[$i]);
> > // convert $results into futures somehow -- though actually doesn't =
look like it is
> > possible.
> > $results =3D async\awaitAll($results);
> >
>=20
> `Future` can be obtained via `getFuture()`, according to the current R=
FC.
> ```php
> async\async(fn($f) =3D> file_get_contents($f), $file[$i])->getFuture();
> ``` =20
> And this semantics can be simplified to: =20
> ```async file_get_contents($file[$i]);```
> or
> ```spawn file_get_contents($file[$i]);```
>=20
> From this perspective, I like that any function can be called with `sp=
awn/async` without worrying about its internals or modifying its code. T=
he pros and cons of this approach are well known. =20

Yes, that is much much nicer! It feel familiar to go:

go file_get_contents($file[$i])

And yes, I realize that would be a fun error in go, but you get the gist.

=E2=80=94 Rob
--7bf96d7fa1cf41bc9a51865a5b055a31
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div><br></div><div>=
<br></div><div>On Sat, Mar 8, 2025, at 09:24, Edmond Dantes wrote:<br></=
div><blockquote type=3D"cite" id=3D"qt" style=3D""><div dir=3D"ltr"><div=
>&gt;&nbsp;<br></div><div>&gt;for($i =3D 0; $i &lt; 10; $i++) $results[]=
 =3D async\async(fn($f) =3D&gt; file_get_contents($f),<br></div><div>&gt=
; $file[$i]);<br></div><div>&gt; // convert $results into futures someho=
w -- though actually doesn't look like it is<br></div><div>&gt; possible=
.<br></div><div>&gt; $results =3D async\awaitAll($results);<br></div><di=
v>&gt;<br></div><div><br></div><div><code>Future</code> can be obtained =
via <code>getFuture()</code>, according to the current RFC.<br></div><di=
v>```php<br></div><div><div>async\async(fn($f) =3D&gt; file_get_contents=
($f), $file[$i])-&gt;getFuture();<br></div><div>```&nbsp;&nbsp;<br></div=
></div><div><div>And this semantics can be simplified to:&nbsp;&nbsp;<br=
></div><div>```async file_get_contents($file[$i]);```<br></div><div>or<b=
r></div><div>```spawn file_get_contents($file[$i]);```<br></div></div><d=
iv><br></div><div>From this perspective, I like that any function can be=
 called with <code>spawn/async</code> without worrying about its interna=
ls or modifying its code. The pros and cons of this approach are well kn=
own.&nbsp;&nbsp;<br></div></div></blockquote><div><br></div><div>Yes, th=
at is much much nicer! It feel familiar to go:<br></div><div><br></div><=
div>go file_get_contents($file[$i])<br></div><div><br></div><div>And yes=
, I realize that would be a fun error in go, but you get the gist.</div>=
<div><br></div><div id=3D"sig121229152">=E2=80=94 Rob<br></div></body></=
html>
--7bf96d7fa1cf41bc9a51865a5b055a31--