Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113161 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 17729 invoked from network); 12 Feb 2021 22:01:59 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 12 Feb 2021 22:01:59 -0000 To: internals@lists.php.net References: Date: Fri, 12 Feb 2021 21:47:48 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Posted-By: 87.81.129.66 Subject: Re: [PHP-DEV] [RFC] Fibers From: marandall@php.net (Mark Randall) Message-ID: 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