Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129303
Precedence: list
MIME-Version: 1.0
Date: Wed, 19 Nov 2025 15:17:35 +0100
To: Edmond Dantes <edmond.ht@gmail.com>
Cc: php internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] [VOTE] True Async RFC 1.6
In-Reply-To: <CAMW7n8D0QshP8VhGOUqVnC+Uwf88TC_yy_mQdeNZW_go5YLdcw@mail.gmail.com>
References: <CAMW7n8D0QshP8VhGOUqVnC+Uwf88TC_yy_mQdeNZW_go5YLdcw@mail.gmail.com>
Message-ID: <21911eecbb08cd0845784e54b942e0da@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

Am 2025-11-19 13:35, schrieb Edmond Dantes:
> According to all previous discussions, version 1.6 of this RFC has
> been prepared and is now being submitted for a vote:
> 
> Voting Page: https://wiki.php.net/rfc/true_async/voting
> RFC https://wiki.php.net/rfc/true_async
> 
> The vote officially starts tomorrow, as previously announced.
> 

I'm seeing that you added the full API stub of the proposed API on 
November 13 (which I'm only seeing now, did I miss an email where you 
mentioned that you made the change?). I'm afraid to note that the 
proposed API is in violation of our policy regarding Throwables: 
https://github.com/php/policies/blob/main/coding-standards-and-naming.rst#throwables. 
Particularly, there the “base exception” for the Async namespace is 
missing. I'm only noticing it now with the stub, since the exact class 
hierarchy was not mentioned in the RFC before.

Given the policy violation I believe that the RFC is unfit to go to vote 
in the current state.

Best regards
Tim Düsterhus