Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128895
Precedence: list
MIME-Version: 1.0
References: <CAMW7n8DGbFnQzjt3s9CcOBwhp+MUOV+K3U=yY=ULOTdUXaOLHQ@mail.gmail.com>
 <0e4e39d6-9cc9-4970-92e0-2463143b4011@app.fastmail.com> <CAMW7n8AgHnO0rBjqBkHNhfvV5PBNxwgHBJ762N3FtVxoh5WnOQ@mail.gmail.com>
 <E8D4A549-79EA-48E9-9D20-3608F357F227@trowski.com> <CAMW7n8D0wMNQE0zuMhbHstyZsDw=e7ryPPZERn11UFV7knmR-g@mail.gmail.com>
 <37180d8d-85b4-49a3-a672-334bf4329470@app.fastmail.com> <CAMW7n8AFaUByiJ=2frgkAFWNPWHS2wYyHiKfwf8dzT7AYnLjWg@mail.gmail.com>
 <2f8524a7-dea2-4fbf-933a-c538d3706253@app.fastmail.com>
In-Reply-To: <2f8524a7-dea2-4fbf-933a-c538d3706253@app.fastmail.com>
Date: Wed, 22 Oct 2025 11:34:37 +0300
Message-ID: <CAMW7n8DKB+AWp2sWPi_w8ZgLQ_zS2MPNgP6n1G5127Nkk7EgOA@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async RFC Stage 4
To: Rob Landers <rob@bottled.codes>
Cc: Aaron Piotrowski <aaron@trowski.com>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: edmond.ht@gmail.com (Edmond Dantes)

> A simpler solution might be to keep things as they are, but have the non-=
idempotent constructs be generators of Awaitable instead of non-idempotent =
Awaitables
So it=E2=80=99s the same as in C#?

The problem with this situation is that so far I haven=E2=80=99t been able =
to
find any cases proving that a non-Future object could cause serious
failures in the code.

At the same time, if a select case expression is introduced in the
future, it would make more sense for select to work with an awaitable
object rather than a Future.

That=E2=80=99s why I=E2=80=99m not yet sure it=E2=80=99s worth abandoning t=
he general behavior
unless a convincing argument is found showing that it leads to real
problems.

-- Ed