Re: PHP True Async RFC Stage 4

From: Date: Thu, 23 Oct 2025 06:40:28 +0000
Subject: Re: PHP True Async RFC Stage 4
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17  Groups: php.internals 
Request: Send a blank email to internals+get-128916@lists.php.net to get a copy of this message
On Thu, Oct 23, 2025, at 07:56, Edmond Dantes wrote:
> Hi,
> 
> > The RFC should include a description of _why_ cooperative cancellation has been chosen.
> If I add detailed explanations for every _why_ in the RFC, it might
> never get read :)
> 
> Thanks, Ed
> 

If someone opens a PR to fix a bug or an RFC that builds on this and there is question of whether
the bug is actually a feature or if it should be done a different way — years from now — often
the only thing to go off of is the reasoning in the RFC. See the recent Readonly Property Hooks
discussion for an example, where it was different people interpreting the same near-decade-old RFC
different ways. Spelling it out might feel long-winded, but it is already long… a few more pages
won’t hurt.

— Rob


Thread (104 messages)

« previous php.internals (#128916) next »