Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129451
Precedence: list
MIME-Version: 1.0
References: <CAMW7n8Dogjj2JFJBNArk-BfvOHRqHKMAFReXJAhDm2UPV1TF7A@mail.gmail.com>
 <92865666.4510.1763818506332@email.ionos.de> <CAMW7n8AycfX4NMfjJ+GzFsPqRaSae-t7Cm3H5z8apRzXUgaVZw@mail.gmail.com>
 <329450798.8037.1763822426377@email.ionos.de> <CAMW7n8DTt2S_RfcyshERixed=qqyFUPEvWp_MpgpW_CvH3urXQ@mail.gmail.com>
 <CAMW7n8CUQxqh4_rTWQBcj+t17i5oW7x-V96FSkwZL85Z2pzrRw@mail.gmail.com>
 <CAB9bCb34cmu9=an9K4rubPSVEDwyWH-rMAVtTTYa3U-LA+GJ+A@mail.gmail.com>
 <CAMW7n8DM4MCP25gSLBbd3+Awzs2+p6Qs_jPgx1mk=RjSVe+iUw@mail.gmail.com>
 <9287c46c-bc63-4dd0-9792-0f9421959589@rwec.co.uk> <CAMW7n8AhbBawCBtfNJZ6XzFSvwhtZotfgBmb1O4CDZ+J2jxt2w@mail.gmail.com>
 <C766271D-EE7A-4727-8A7C-B117429768E5@rwec.co.uk> <CAMW7n8Bk+AhbXjg8QADFo=2k9qCE54DD68Hxkf2k_9J=EFboUQ@mail.gmail.com>
 <65869feb-d518-4de3-8c10-115e3ba7dce7@rwec.co.uk> <CAMW7n8CA6gfdWzhVCY3j4w_=S-rZW5sUvkSL_e4+hc_Ka+r1rA@mail.gmail.com>
 <55149f3e-7ec7-4479-bd6d-2e7fe1b8edef@rwec.co.uk> <CAMW7n8Cfs9+wEpGVp5C2VL3ey8vKUNS2NyJAq+w7-DJXg172Dw@mail.gmail.com>
 <19693420-c091-49b7-b557-e09717239d9b@rwec.co.uk> <CAMW7n8DUGhai5v95_5Nv6Vxuj1CuhmnFOVnAPVW2ao37agQkzw@mail.gmail.com>
 <c9d5cc10-9605-45ee-9d06-9a66de4d71a2@app.fastmail.com>
In-Reply-To: <c9d5cc10-9605-45ee-9d06-9a66de4d71a2@app.fastmail.com>
Date: Tue, 25 Nov 2025 12:03:48 +0100
Message-ID: <CAB9bCb0R4dt4g6Ed6XKAh9HU-8=dMqiyw1j71-M-z9Lu2=uU6A@mail.gmail.com>
Subject: Re: [PHP-DEV] [VOTE] True Async RFC 1.6
To: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: bart+php@croquemonsieur.be (Bart Vanhoutte)

Op di 25 nov 2025 om 11:36 schreef Rob Landers <rob@bottled.codes>:
>
>
> If we're going to have to recreate some of the most basic interfaces to g=
et async to work ... does it make sense to seriously consider coloured func=
tions? As annoying as it would be to refactor so much code, I think we coul=
d realistically provide ourselves escape hatches by not requiring every fun=
ction calling `await` to be async?
>

I have worked with coloured functions in PHP when Fibers were not
around and the developer experience is very bad. Before PHP 8.1; every
function I wrote would be coloured by either accepting or returning a
Promise<sometype> (which is made worse by the fact there's no
generics).

Since PHP 8.1; I can use Fibers and implement a widely spread
Interface in an async way. Currently, if I want to use an SDK client,
the first thing that I check is `composer.json` to find out what HTTP
client it uses. If it accepts a PSR-18 ClientInterface I use a small
wrapper around ReactPHP's Browser that awaits a Promise and I'm set.
We've been talking about shared state and possible breaks in backwards
compatibility, but I must say that in reality it's not something that
I find being in the way very often. Like I've made it seem before, if
there's any serious breaks in backward compatibility (not the order of
log lines that might be different from the sync implementation) I
would at that point just document the change and release a new major
version of a library. That is a lot less painful imo than working with
coloured functions.

Best Regards,
Bart