Re: [VOTE] True Async RFC 1.6
| From: | Edmond Dantes | Date: | Sun, 23 Nov 2025 19:09:59 +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 17 18 19 20 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-129416@lists.php.net to get a copy of this message | ||
Hello.
> @Ed Unless something calls
spawn all I/O is going to be
> blocking &
> non-concurrent, correct?
Yes.
If no one calls spawn, this is equivalent to the code running inside a
single coroutine.
At the moment, TrueAsync has an internal flag that allows it to be
enabled or disabled. If Async is disabled, an exception will be
thrown.
So essentially this capability already exists in the code, and the
global flag that turns the feature on or off was inherited from the
early versions of the library.