Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129379
Precedence: list
MIME-Version: 1.0
References: <CAMW7n8D0QshP8VhGOUqVnC+Uwf88TC_yy_mQdeNZW_go5YLdcw@mail.gmail.com>
 <C58ADF49-6E21-4E25-8859-2A0769829E38@php.net> <e8625214-1c6f-40b8-b24f-e592e6f92012@beccati.com>
 <CAMW7n8Dy3=QyCrG4BMwVXWAipgOr2Vyhy_jbLVTYeq2Jc5v15g@mail.gmail.com>
 <dbc31109-a43d-4afc-9f4f-62c6439328e5@rwec.co.uk> <ea59722c-2c84-4a59-a442-a8b217ff577d@gmail.com>
 <b151687a-f4bd-48cf-90e6-440f763ccd6b@rwec.co.uk> <CAMW7n8CLZ7yFhUhh89wx7L+YwQ25LA7HZoGWUFB3R76KgXko2w@mail.gmail.com>
 <CAEKnhAHRPbiU4auDuTtFL2ueNnACjmYm_ff9c3VciYE9HfeGZg@mail.gmail.com>
 <CAMW7n8D5B=XVX_Jes+LV=2fPwjQr_RBVphPi_Cxm8-_Rwpdo_Q@mail.gmail.com>
 <CADK1yX+jGtqQVYFTo5YmkenPrNcXz7Dd7RCUKWGrq+50pnKOnw@mail.gmail.com>
 <CAMW7n8Dogjj2JFJBNArk-BfvOHRqHKMAFReXJAhDm2UPV1TF7A@mail.gmail.com>
 <CADK1yXKgkuKmOMB7KA9GNQMtpNw7ZgWcPEPE_Uhr_+8eReDCEA@mail.gmail.com>
 <CAMW7n8D+RGAFDY3oGnzaAabrhW9TOMeBgtvx4zCy3AoBUb5szA@mail.gmail.com> <CAEKnhAFsXpfZy8FQyA4Z9bNyNa26rCCn5GO=oQ274e1K2+GkAw@mail.gmail.com>
In-Reply-To: <CAEKnhAFsXpfZy8FQyA4Z9bNyNa26rCCn5GO=oQ274e1K2+GkAw@mail.gmail.com>
Date: Fri, 21 Nov 2025 17:07:15 -0300
Message-ID: <CAJ6fn9PR2EpnJS17Ri7oGL5Mq0Ng2EX+oxJEqD9-fR0dxSmK=g@mail.gmail.com>
Subject: Re: [PHP-DEV] [VOTE] True Async RFC 1.6
To: Jakub Zelenka <bukka@php.net>
Cc: Edmond Dantes <edmond.ht@gmail.com>, Deleu <deleugyn@gmail.com>, 
	"Rowan Tommins [IMSoP]" <imsop.php@rwec.co.uk>, internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000e9e28e0644205cba"
From: luisvscbarros@gmail.com (=?UTF-8?Q?Lu=C3=ADs_Vin=C3=ADcius_Santos_da_Costa_Barros?=)

--000000000000e9e28e0644205cba
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=99t p=
ossible,
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=C3=ADs Vin=C3=ADcius.

Em sex., 21 de nov. de 2025, 16:45, Jakub Zelenka <bukka@php.net> escreveu:

>
>
> On Fri, Nov 21, 2025 at 3:22=E2=80=AFPM Edmond Dantes <edmond.ht@gmail.co=
m> wrote:
>
>> Hello
>>
>> > how do I keep my project always-sync without risking one of my compose=
r
>> 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
>
>
>

--000000000000e9e28e0644205cba
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Hello, from a Brazil that is (as always) very, very, very=
 hot.<div dir=3D"auto"><br></div><div dir=3D"auto">I believe that using a p=
hp.ini flag would be the approach that makes the most sense, especially in =
an experimental stage. Since that isn=E2=80=99t 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.</div><=
div dir=3D"auto"><br></div><div dir=3D"auto">Sincerely,</div><div dir=3D"au=
to">Lu=C3=ADs Vin=C3=ADcius.</div></div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">Em sex., 21 de nov. de 2025, 16:45, Jakub=
 Zelenka &lt;<a href=3D"mailto:bukka@php.net" target=3D"_blank" rel=3D"nore=
ferrer">bukka@php.net</a>&gt; escreveu:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex"><div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_qu=
ote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Nov 21, 2025 at 3:22=E2=
=80=AFPM Edmond Dantes &lt;<a href=3D"mailto:edmond.ht@gmail.com" rel=3D"no=
referrer noreferrer" target=3D"_blank">edmond.ht@gmail.com</a>&gt; wrote:<b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello<br>
<br>
&gt; how do I keep my project always-sync without risking one of my compose=
r packages suddenly calling spawn() and causing bugs I have no idea how to =
even begin to understand?<br>
<br>
This idea was mentioned a bit earlier in the discussion. You can use a<br>
special setting to disable asynchrony. There are many different<br>
possibilities here. For example, you can tell Composer not to use<br>
async packages. And so on. You can come up with your own protection<br>
mechanisms. There is no technical problem here in terms of<br>
implementation.<br>
Why not enable asynchronous mode in PHP explicitly through php.ini?<br></bl=
ockquote><div><br></div><div>I&#39;m not sure if INI is going to be success=
ful. I would bet that it is going to get rejected as PHP has been moving ag=
ainst introducing INI for language / extension behavior changes.</div><div>=
<br></div><div>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 stri=
ct types. I haven&#39;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.</div><div><br></div><div>Cheers</div><div><br></div><div>Jakub</=
div><div><br></div><div><br></div></div></div>
</blockquote></div>

--000000000000e9e28e0644205cba--