Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128892
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>
In-Reply-To: <37180d8d-85b4-49a3-a672-334bf4329470@app.fastmail.com>
Date: Wed, 22 Oct 2025 07:32:36 +0300
Message-ID: <CAMW7n8AFaUByiJ=2frgkAFWNPWHS2wYyHiKfwf8dzT7AYnLjWg@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)

Hi

> I don=E2=80=99t think it=E2=80=99s a =E2=80=9Crule=E2=80=9D per se and wh=
y I suggested breaking it up into two different kinds of Awaitables.
> Invariants make code easier to reason about and work with. The more invar=
iants you have, the easier it is to form, maintain, and refactor.

So that is the rule: **invariants make code easier to understand**.
A more general principle is stated as follows: reducing complexity.

I think this point needs some thought.
If the await operation is allowed only for Future, it will make the
code more consistent which is a good thing.

Then it will be necessary to add a FutureInterface, and Awaitable
should be hidden from the UserLand namespace.