Re: PHP True Async RFC

From: Date: Sat, 08 Mar 2025 08:24:52 +0000
Subject: Re: PHP True Async RFC
References: 1 2 3 4 5 6 7 8 9 10 11 12  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
>
>for($i = 0; $i < 10; $i++) $results[] = async\async(fn($f) =>
file_get_contents($f),
> $file[$i]);
> // convert $results into futures somehow -- though actually doesn't look
like it is
> possible.
> $results = async\awaitAll($results);
>

Future can be obtained via getFuture(), according to the current RFC.
```php
async\async(fn($f) => file_get_contents($f), $file[$i])->getFuture();
```

And this semantics can be simplified to:
``async file_get_contents($file[$i]);``
or
``spawn file_get_contents($file[$i]);``

From this perspective, I like that any function can be called with
spawn/async without worrying about its internals or modifying its code. The
pros and cons of this approach are well known.


Thread (110 messages)

« previous php.internals (#126636) next »