Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129042
Precedence: list
MIME-Version: 1.0
References: <CAMW7n8DiWK6y=76cRTpx+6eGmBgytd2HWs2C-OH5rd8WNLffFA@mail.gmail.com>
 <2441aa9c-41c8-4ce1-b9c0-67136e5f97da@dennis.birkholz.biz>
 <CAMW7n8A6A-61Q1dzvQxhud0WYQdOKdANqmRbgNg2o=-Qyg5snA@mail.gmail.com> <ccb69ad4-5875-4bf4-92c7-50d1bd677ff2@dennis.birkholz.biz>
In-Reply-To: <ccb69ad4-5875-4bf4-92c7-50d1bd677ff2@dennis.birkholz.biz>
Date: Sat, 1 Nov 2025 18:00:10 +0200
Message-ID: <CAMW7n8BWxG=hP2fOkdS5bEiC_P0bSvb0GUosqN=oUiCAZhsnTw@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async RFC Stage 5
To: Dennis Birkholz <php@dennis.birkholz.biz>
Cc: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: edmond.ht@gmail.com (Edmond Dantes)

>  From the standpoint of PHP language user, I have a completely different =
view on Fibers vs. Corotines.
That=E2=80=99s sad.

> They look very similar from the outside
Coroutines and Fibers have completely different behavior. I hope
you=E2=80=99re not comparing them just by appearance?

> I really belief we should avoid fragmentation and enhance/adjust Fibers t=
o meet the memory and performance requirements of a Coroutine.
But the problem has already happened, and it=E2=80=99s not directly related=
 to this RFC.
Of course, there=E2=80=99s a possibility to bridge the two worlds by callin=
g
PHP functions from C, but as I=E2=80=99ve said before: just because somethi=
ng
can be done doesn=E2=80=99t mean it should be done.

> If the provided awaitable is itself some infinitely blocking Coroutine (e=
.g. while (true) {}),

If you have a coroutine with an infinite loop, it means other
coroutines will never get control.
(more about it by searching for the keyword: =E2=80=9Cconcurrency")

The RFC contains an example that isn=E2=80=99t very elegant from a semantic
point of view, but is completely correct in terms of logic:
```php
// Await task 1, but no longer than 5 seconds.
await($task1, spawn(sleep(...), 5));
```

And here=E2=80=99s another piece of code (Async\Signal is not present in th=
e
RFC, but it=E2=80=99s entirely possible.):
```php
// Await task 1 until a signal occurs.
await($task1, new Async\Signal(SIG_TERM));
```

> In addition, what happens if a Coroutine is suspended and is restarted ag=
ain.

The Await function waits for the coroutine to complete.
The suspended state does not affect the waiting process.
The wait is interrupted for two reasons: an unhandled exception or the
coroutine=E2=80=99s completion.

All of this is described in the RFC: https://wiki.php.net/rfc/true_async#aw=
ait

---
Ed