Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129819
Precedence: list
MIME-Version: 1.0
References: <CAMW7n8B9XHzF5ND21-hNYtw26EnE+0b+W0Nv=wb_ayMmu4CbKw@mail.gmail.com>
In-Reply-To: <CAMW7n8B9XHzF5ND21-hNYtw26EnE+0b+W0Nv=wb_ayMmu4CbKw@mail.gmail.com>
Date: Wed, 21 Jan 2026 19:35:25 +0100
Message-ID: <CAEKnhAEF1UFP0P+XbvK65ywz6c1OQPZHsfLXPrfyjP3Zp=p5Lg@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] True Async RFC 1.7
To: Edmond Dantes <edmond.ht@gmail.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000cef1ee0648ea301e"
From: bukka@php.net (Jakub Zelenka)

--000000000000cef1ee0648ea301e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

On Thu, Dec 25, 2025 at 9:00=E2=80=AFAM Edmond Dantes <edmond.ht@gmail.com>=
 wrote:

> Hello everyone!
>
> RFC https://wiki.php.net/rfc/true_async
>
> Here is the seventh version of the RFC, revised and expanded.
>
> ## Version 1.7 (December 2025)
>
> - **Fiber integration:** added `Fiber::getCoroutine()` method,
> ownership model, deadlock resolution
> - Added Coroutine methods: `getId()`, `getResult()`, `getException()`,
> `getTrace()`
> - Refined *Goals* section: improved clarity and technical accuracy of
> core value propositions
> - Function naming aligned with PHP coding standards:
>   `currentCoroutine()` =E2=86=92 `current_coroutine()`,
>   `gracefulShutdown()` =E2=86=92 `shutdown()`,
>   `getCoroutines()` =E2=86=92 `get_coroutines()`
> - Method renaming: `Coroutine::onFinally()` =E2=86=92 `Coroutine::finally=
()`
> (brevity)
> - Interface renaming: `FutureLike` =E2=86=92 `Completable`
> - Exception renaming: `CancellationError` =E2=86=92 `Cancellation` (clear=
er
> semantics)
> - Moved `Cancellation` to the **root namespace** (`\Cancellation`) as
> a fundamental PHP mechanism
> - Changed `Cancellation` inheritance from `\Error` to `\Throwable`,
> following Python=E2=80=99s `CancelledError` pattern
> - Added backward compatibility notes for the new root namespace class
> - Renamed `DeadlockException` to `DeadlockCancellation`
>
>
I think it would be more reasonable to target 9.0. We were discussing it
and it might potentially happen after 8.6 or in the worst case in the
following release (after 8.7) if we have a big TODO list of things (another
thing that we want there is conversion of streams from resources to
objects). We could potentially manage it as some sort of release branch
(that would need to be agreed) but I think it would be more reasonable for
feature like this as it would give us time to properly stabilise it.

Kind regards,

Jakub

--000000000000cef1ee0648ea301e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi,</div><br><div class=3D"gmail_quote gmail_quote_co=
ntainer"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Dec 25, 2025 at 9:00=
=E2=80=AFAM Edmond Dantes &lt;<a href=3D"mailto:edmond.ht@gmail.com">edmond=
.ht@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">Hello everyone!<br>
<br>
RFC <a href=3D"https://wiki.php.net/rfc/true_async" rel=3D"noreferrer" targ=
et=3D"_blank">https://wiki.php.net/rfc/true_async</a><br>
<br>
Here is the seventh version of the RFC, revised and expanded.<br>
<br>
## Version 1.7 (December 2025)<br>
<br>
- **Fiber integration:** added `Fiber::getCoroutine()` method,<br>
ownership model, deadlock resolution<br>
- Added Coroutine methods: `getId()`, `getResult()`, `getException()`,<br>
`getTrace()`<br>
- Refined *Goals* section: improved clarity and technical accuracy of<br>
core value propositions<br>
- Function naming aligned with PHP coding standards:<br>
=C2=A0 `currentCoroutine()` =E2=86=92 `current_coroutine()`,<br>
=C2=A0 `gracefulShutdown()` =E2=86=92 `shutdown()`,<br>
=C2=A0 `getCoroutines()` =E2=86=92 `get_coroutines()`<br>
- Method renaming: `Coroutine::onFinally()` =E2=86=92 `Coroutine::finally()=
` (brevity)<br>
- Interface renaming: `FutureLike` =E2=86=92 `Completable`<br>
- Exception renaming: `CancellationError` =E2=86=92 `Cancellation` (clearer=
 semantics)<br>
- Moved `Cancellation` to the **root namespace** (`\Cancellation`) as<br>
a fundamental PHP mechanism<br>
- Changed `Cancellation` inheritance from `\Error` to `\Throwable`,<br>
following Python=E2=80=99s `CancelledError` pattern<br>
- Added backward compatibility notes for the new root namespace class<br>
- Renamed `DeadlockException` to `DeadlockCancellation`<br><br></blockquote=
><div><br></div><div>I think it would be more reasonable to target 9.0. We =
were discussing it and it might potentially happen after 8.6 or in the wors=
t case in the following release (after 8.7) if we have a big TODO list of t=
hings (another thing that we want there is conversion of streams from resou=
rces to objects). We could potentially manage it as some sort of release br=
anch (that would need to be agreed) but I think it would be more reasonable=
 for feature like this as it would give us time to properly stabilise it.</=
div><div><br></div><div>Kind regards,</div><div><br></div><div>Jakub</div><=
/div></div>

--000000000000cef1ee0648ea301e--