Re: [RFC] Fibers

From: Date: Fri, 12 Feb 2021 22:05:07 +0000
Subject: Re: [RFC] Fibers
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-113162@lists.php.net to get a copy of this message

> On Feb 12, 2021, at 3:47 PM, Mark Randall <marandall@php.net> wrote:
> 
> On 12/02/2021 21:40, Aaron Piotrowski wrote:
>> I would like to open voting for this RFC around the beginning of March, so please review
>> the minimal API and provide any feedback soon.
> 
> Removing the scheduler was likely a good plan, but pretty please reconsider your future scope.
> 
> It's going to be a really big pain to push people to use this functionality, only to have
> to re-write it 1 or 2 year later because a vastly superior syntax mechanism was introduced.
> 
> If you can add async / await / delay / defer, even if it takes another month or so, that would
> likely make this RFC have a significantly bigger and more beneficial impact on userland.
> 
> Mark Randall
> 
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
> 


Hi Mark,

The Fiber API is only tangentially related to async / await, etc. Adding such a feature is a much
larger proposal and would not be small undertaking. The future scope proposes using fibers in an
async / await implementation, but async / await would not replace fibers.

The Fiber API would conflict or prevent async / await from being added to PHP in the future. The two
APIs can coexist and serve different purposes.

Cheers,
Aaron Piotrowski


Thread (29 messages)

« previous php.internals (#113162) next »