Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126638
Precedence: bulk
MIME-Version: 1.0
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>
 <62505751-7d35-4ffd-ace2-cbf099ee2b8c@app.fastmail.com>
In-Reply-To: <62505751-7d35-4ffd-ace2-cbf099ee2b8c@app.fastmail.com>
Date: Sat, 8 Mar 2025 10:59:45 +0200
Message-ID: <CAM0CcxggBffuCA-K0ETd7EwMThm37k8d3ny+77xgjTEhGyL7ZQ@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async RFC
To: Rob Landers <rob@bottled.codes>
Cc: Edmond Dantes <edmond.ht@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000008b5567062fd0f618"
From: zsidelnik@gmail.com (Eugene Sidelnyk)

--0000000000008b5567062fd0f618
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

>
> 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
>

Yes, that's the point that we don't bother client code with any of the
async stuff =F0=9F=99=82

If we want to create "async space" for functions to have switching on IO,
only then do we call them like this, and the await'em all with awaitAll =F0=
=9F=99=82.

>

--0000000000008b5567062fd0f618
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br></div><div dir=3D"auto"><div class=3D"gmail_quot=
e gmail_quote_container"><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><br></div=
><div>Yes, that 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"m_-5897737967963498298sig121229152">=E2=80=94=
 Rob<br></div></div></blockquote></div></div><div dir=3D"auto"><br></div><d=
iv dir=3D"auto">Yes, that&#39;s the point that we don&#39;t bother client c=
ode with any of the async stuff =F0=9F=99=82=C2=A0</div><div dir=3D"auto"><=
br></div><div dir=3D"auto">If we want to create &quot;async space&quot; for=
 functions to have switching on IO, only then do we call them like this, an=
d the await&#39;em all with awaitAll =F0=9F=99=82.</div><div dir=3D"auto"><=
div class=3D"gmail_quote gmail_quote_container"><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><div><div id=3D"m_-5897737967963498298sig121229152"></div></div></block=
quote></div></div></div>

--0000000000008b5567062fd0f618--