Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128980
Feedback-ID: i8414410d:Fastmail
Precedence: list
MIME-Version: 1.0
Date: Mon, 27 Oct 2025 11:02:03 -0500
To: "php internals" <internals@lists.php.net>
Message-ID: <889d3042-7b3e-4152-bd8c-09bbcc967309@app.fastmail.com>
In-Reply-To: 
 <CAMW7n8BxmAC56LZ4qA6oJp0kFhhPMuLdqfmzeSVQrf6woR9GyA@mail.gmail.com>
References: 
 <CAMW7n8DGbFnQzjt3s9CcOBwhp+MUOV+K3U=yY=ULOTdUXaOLHQ@mail.gmail.com>
 <CAMW7n8BxmAC56LZ4qA6oJp0kFhhPMuLdqfmzeSVQrf6woR9GyA@mail.gmail.com>
Subject: Re: [PHP-DEV] Re: PHP True Async RFC Stage 4
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: larry@garfieldtech.com ("Larry Garfield")

On Mon, Oct 27, 2025, at 7:08 AM, Edmond Dantes wrote:
> Hello all.
>
> ### Current work and discussion plan for this RFC
>
> 1. By the end of this week, the proposed changes at
>    
> [https://github.com/true-async/php-true-async-rfc/issues](https://github.com/true-async/php-true-async-rfc/issues)
>    will be accepted if no objections are raised.
>
> 2. After that, the RFC document will be updated, and a new **2-week
> discussion period** will begin.
>
> 3. After the new changes are accepted, the RFC will be updated again,
> and the process will repeat.
>
> The discussion will be extended as long as necessary, including at the
> request of the participants.
>
> ---
> With best regards,
> Ed

I am not sure how feasible this is, but would there be a way to split the "async toggle" of IO operations off to its own PR/RFC?  To me, that is by far the most important part of this RFC as that's the biggest blocker for wider async adoption, but I'm not sure how many layers are needed above it to make it possible to toggle in a safe fashion.

--Larry Garfield