Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128881
Precedence: list
MIME-Version: 1.0
References: <CAMW7n8DGbFnQzjt3s9CcOBwhp+MUOV+K3U=yY=ULOTdUXaOLHQ@mail.gmail.com>
 <0e4e39d6-9cc9-4970-92e0-2463143b4011@app.fastmail.com>
In-Reply-To: <0e4e39d6-9cc9-4970-92e0-2463143b4011@app.fastmail.com>
Date: Tue, 21 Oct 2025 17:56:25 +0300
Message-ID: <CAMW7n8AgHnO0rBjqBkHNhfvV5PBNxwgHBJ762N3FtVxoh5WnOQ@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP True Async RFC Stage 4
To: Rob Landers <rob@bottled.codes>
Cc: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: edmond.ht@gmail.com (Edmond Dantes)

> This seems a bit contradictory and confuses things. When I await(), do I =
need to do it in a loop, or just once?
> It might be a good idea to make a couple subtypes: Signal and Future. Cor=
outines become Future that only await once, while Signal is something that =
can be awaited many times.

I made a mistake in my previous response, and it requires clarification.
Classes that can be awaited multiple times are indeed possible.
These include `TimeInterval`, `Channel`, `FileSystemEvent`, as well as
I/O triggers.

All of these classes can be `Awaitable`.
This is done to allow bulk waiting on objects, regardless of how they
work internally.
So this is meant for functions like `awaitXX`, although such behavior
is also possible for the `await()` function itself:

```php
$timeInterval =3D new Async\TimeInterval(1000);
while(true) {
    await($timeInterval);
}
```

As for objects of type `Future`, it=E2=80=99s clear that in future RFCs the=
re
will be a `FutureInterface`, which will be implemented by coroutines.