Re: PHP True Async RFC
| From: | Edmond Dantes | Date: | Sat, 08 Mar 2025 07:32:39 +0000 |
| Subject: | Re: PHP True Async RFC | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-126630@lists.php.net to get a copy of this message | ||
>
> Let's assume we want to support this scenario; we could:
>
Thank you, that's an accurate summary. I would focus on two options:
1. Creating child coroutines by default, but allowing unbound ones to
exist.
2. Explicitly creating child coroutines.
And in the RFC, I would leave the choice open to all participants.
In terms of syntax, it might look something like this (just thinking out
loud):
```php
async {
async child {
}
}
```
or
```php
async {
async unbound {
}
}
```
The pros and cons were described earlier and will be moved to a separate
RFC.