Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129248
Precedence: list
MIME-Version: 1.0
References: <CAMW7n8DiWK6y=76cRTpx+6eGmBgytd2HWs2C-OH5rd8WNLffFA@mail.gmail.com>
 <CAMW7n8Dp3siTp0NKGc=-8aNg=Mqoxug9Osgn2399P1v4wi3n5Q@mail.gmail.com>
 <6618a91c-5393-4f40-88b5-b5041ee09deb@app.fastmail.com> <CAMW7n8CeDFSaN0e4Kr=1jrJyHEonHokfxcY4gdf6L3FqdH1FZQ@mail.gmail.com>
 <3e0cf0a1-c1a3-4e05-97ba-0eeb7f559a53@app.fastmail.com> <CAMW7n8AX7O7x99KGdPSai6sPP1Xd6V4ojQ7CEWmxthNLPM2hyQ@mail.gmail.com>
 <d17e07bf-9664-48e8-b7c4-39142f3cfbf2@app.fastmail.com> <CAEKnhAHp9fCOD0NCLE9J25dTkVd72csHGb3HGwATg+qyxNaFwg@mail.gmail.com>
 <41c5eed0-dd1b-4ea4-99cf-f6d16682bd7f@app.fastmail.com> <CAEKnhAEmSZn=Tr24YC9wxAUk1NPM529GR_iBWmX=fKpXxpuXRg@mail.gmail.com>
 <f777dba4-b29f-4744-889e-131ec730e305@app.fastmail.com>
In-Reply-To: <f777dba4-b29f-4744-889e-131ec730e305@app.fastmail.com>
Date: Sun, 16 Nov 2025 00:06:30 +0200
Message-ID: <CAMW7n8AovFXC6by4AyAwh0U9Gax2UQ-MkkpwqCPkP8hNz52hew@mail.gmail.com>
Subject: Re: [PHP-DEV] Re: PHP True Async RFC Stage 5
To: Rob Landers <rob@bottled.codes>
Cc: Jakub Zelenka <bukka@php.net>, php internals <internals@lists.php.net>, 
	Larry Garfield <larry@garfieldtech.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: edmond.ht@gmail.com (Edmond Dantes)

> I guess my main thing is that this RFC should only cover coroutine machin=
ery: it should not promise "transparent async" or "code

It=E2=80=99s like trying to dig a hole with half a shovel :)

> that works exactly the same" OR if it wants to make those claims, it shou=
ld actually demonstrate
> how instead of hand-waving everything as an "implementation detail" when =
none of those claims can actually be validated without those details.

All of my claims are backed by tests :)