Re: [RFC] True Async RFC 1.7

From: Date: Wed, 21 Jan 2026 15:48:14 +0000
Subject: Re: [RFC] True Async RFC 1.7
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-129809@lists.php.net to get a copy of this message
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

« previous php.internals (#129809) next »