Re: PHP True Async RFC
| From: | Larry Garfield | Date: | Sat, 08 Mar 2025 18:10:53 +0000 |
| Subject: | Re: PHP True Async RFC | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-126654@lists.php.net to get a copy of this message | ||
On Sat, Mar 8, 2025, at 8:00 AM, Daniil Gentili wrote:
>> As far as I can tell, the entire reason we are talking about this is because adding the
>> event loop changes the behavior of existing code. So we cannot "just turn it on".
>>
>> I haven't seen an explanation of why this is the case, but that's how we got to
>> this point. We need some way to "opt in" to turning on the event loop.
>
> This also seems like a very bad idea: there is no reason for the
> language hide concurrency behind an INI or even worse a compilation
> flag.
This is beyond a strawman to the point of being a straw-pile. Literally no one has suggested
"hiding concurrency behind an ini flag or compilation flag." Please confine your comments
to those that have some basis is reality and in this thread.
--Larry Garfield