Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129809
Precedence: list
MIME-Version: 1.0
Date: Wed, 21 Jan 2026 16:48:14 +0100
To: Edmond Dantes <edmond.ht@gmail.com>
Cc: php internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] [RFC] True Async RFC 1.7
In-Reply-To: <CAMW7n8B9XHzF5ND21-hNYtw26EnE+0b+W0Nv=wb_ayMmu4CbKw@mail.gmail.com>
References: <CAMW7n8B9XHzF5ND21-hNYtw26EnE+0b+W0Nv=wb_ayMmu4CbKw@mail.gmail.com>
Message-ID: <280b51ba9bed2d72d2d9b8cd9cc68eb8@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-12-25 08:57, schrieb Edmond Dantes:
> - Function naming aligned with PHP coding standards:
>   `currentCoroutine()` → `current_coroutine()`,
>   `gracefulShutdown()` → `shutdown()`,
>   `getCoroutines()` → `get_coroutines()`
> - Method renaming: `Coroutine::onFinally()` → `Coroutine::finally()` 
> (brevity)
> - Interface renaming: `FutureLike` → `Completable`
> - Exception renaming: `CancellationError` → `Cancellation` (clearer 
> semantics)

Having a new discussion thread for each version of the RFC (and the 
amount of changes) make it hard for me to keep up with the RFC.

I've just taken a quick look at the stubs though and am noticing that 
the “base exception” is incorrectly named, as I had previously mentioned 
in my email in the voting thread: 
https://news-web.php.net/php.internals/129308

It should be `class AsyncException extends \Exception {}` and `class 
AsyncCancellation extends \Cancellation { }` as per: 
https://github.com/php/policies/blob/main/coding-standards-and-naming.rst#throwables

Best regards
Tim Düsterhus