Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129216
Precedence: list
MIME-Version: 1.0
References: <CAMW7n8DiWK6y=76cRTpx+6eGmBgytd2HWs2C-OH5rd8WNLffFA@mail.gmail.com>
 <CAMW7n8Dp3siTp0NKGc=-8aNg=Mqoxug9Osgn2399P1v4wi3n5Q@mail.gmail.com> <697c56c5-78bf-407a-a884-74ee150e992c@bastelstu.be>
In-Reply-To: <697c56c5-78bf-407a-a884-74ee150e992c@bastelstu.be>
Date: Thu, 13 Nov 2025 12:26:58 +0200
Message-ID: <CAMW7n8CJ8u0Kw4Fa3VHJaQO8OYNRZTkQ-xZBzCQjepw3z3jkVQ@mail.gmail.com>
Subject: Re: [PHP-DEV] Re: PHP True Async RFC Stage 5
To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>
Cc: php internals <internals@lists.php.net>, Jakub Zelenka <bukka@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)

Hello, Tim.

> What I am missing from the RFC text is some kind of "Executive Summary"
> to make it clear what *is* and what *is not* actually being proposed

I=E2=80=99ll try to look through the text again to see what exactly might b=
e
unclear. Although to be honest, I also don=E2=80=99t really understand what
exactly is unclear.

> This makes it hard for me to see what I am actually voting for
I suggest we do it this way. I=E2=80=99ll write a summary here, and if need=
ed
we can add some of these phrases to the RFC.
I have an idea to format the summary as questions and answers. That
will probably make it easier to understand.

>  I would suggest to add a =E2=80=9Cfull stub=E2=80=9D
+
> Also, please make sure to add the =E2=80=9CAbstain=E2=80=9D option to the=
 vote
I will do it, thanks

> With regard to the relationship with fibers
I will also take these questions into account in the next message.

Thanks, Ed