> Rowan Tommins [IMSoP] <[email protected]> hat am 21.11.2025 21:58 CET > geschrieben: > > > On 21 November 2025 19:42:40 GMT, Jakub Zelenka <[email protected]> wrote: > >I'm not sure if INI is going to be successful. I would bet that it is going > >to get rejected as PHP has been moving against introducing INI for language > >/ extension behavior changes. > > I think Edmond is right that exactly how the "off switch" should look is a > ticket for later in the project. A ticket that blocks the final release, but > doesn't have a deadline other than that. > > The important thing for now is to have a general model of how code behaves > when the switch in the "off" position, and whether or not sync and async code > can run in the same thread, because that has an impact on how other parts of > the design progress. > > > Rowan Tommins > [IMSoP]
Hello, from userland perspective I would prefer explicit declaration on each usage of async over declare(), hooks and INI. This would make reviews, static code analysis, etc. easier. RFCs can be written in small parts for each new function, e.g. $content = \file_get_contents(); // sync $promise = \file_get_contents_async(); // async $promise = \Async\file_get_contents(); // async $contentOrFalse = curl_exec($ch); // sync $promise = \curl_exec_async($ch); // async $promise = \Async\curl_exec($ch); // async $pdoStatement = $pdo->prepare(); // sync $pdoStatementAsync = $pdo->prepare_async(); // async $promise = $pdoStatementAsync->execute() Best Regards Thomas
