Re: PHP True Async RFC Stage 4
| From: | Edmond Dantes | Date: | Wed, 22 Oct 2025 08:34:37 +0000 |
| Subject: | Re: PHP True Async RFC Stage 4 | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-128895@lists.php.net to get a copy of this message | ||
> 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’s the same as in C#?
The problem with this situation is that so far I haven’t 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’s why I’m not yet sure it’s worth abandoning the general behavior
unless a convincing argument is found showing that it leads to real
problems.
-- Ed