Re: [VOTE] True Async RFC 1.6

From: Date: Mon, 24 Nov 2025 16:36:44 +0000
Subject: Re: [VOTE] True Async RFC 1.6
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16  Groups: php.internals 
Request: Send a blank email to internals+get-129439@lists.php.net to get a copy of this message
On 24/11/2025 15:46, Bart Vanhoutte wrote:

If Susie does release a new major version I would expect Les to fix his dependency on shared state before upgrading to a new major version instead of blindly upgrading to a new version*. * which he shouldn't do anyways, async or not.
I already covered that point:
 Legacy Les won't get it until he opts in, but at some point he will need a new version of the library for other reasons (e.g. because the cloud API becomes incompatible with the old library version); so he still needs a way to run it safely.
It is not about Les "blindly upgrading". It is about what he needs to do to consciously, safely upgrade. Remember, he has no interest in running his application asynchronously. He just wants his code to continue running on PHP 9, and to have access to Susie's cloud API. Forcing Susie's code to run more slowly is not a problem for him. Having to rewrite chunks of his application in case they break something is a big problem. -- Rowan Tommins [IMSoP]

Thread (106 messages)

« previous php.internals (#129439) next »