Re: [VOTE] True Async RFC 1.6

Hello, from a Brazil that is (as always) very, very, very hot. I believe that using a php.ini flag would be the approach that makes the most sense, especially in an experimental stage. Since that isn’t possible, I think having a function inside the Async namespace is the best alternative, something like Async\enable(), without a corresponding Async\disable(), of course. Sincerely, Luís Vinícius. Em sex., 21 de nov. de 2025, 16:45, Jakub Zelenka <bukka@php.net> escreveu: > > > On Fri, Nov 21, 2025 at 3:22 PM Edmond Dantes <edmond.ht@gmail.com> wrote: > >> Hello >> >> > how do I keep my project always-sync without risking one of my composer >> packages suddenly calling spawn() and causing bugs I have no idea how to >> even begin to understand? >> >> This idea was mentioned a bit earlier in the discussion. You can use a >> special setting to disable asynchrony. There are many different >> possibilities here. For example, you can tell Composer not to use >> async packages. And so on. You can come up with your own protection >> mechanisms. There is no technical problem here in terms of >> implementation. >> Why not enable asynchronous mode in PHP explicitly through php.ini? >> > > 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. > > It reminds to some extend the scalar type hints with strict / non strict > discussion that ended up using declare keyword. So maybe async could use it > too and it could be enabled per file in a similar way as strict types. I > haven't thought if it would always make sense for async but for projects > that want to be fully async, it would need to be declared in each file. > > Cheers > > Jakub > > >