Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113162 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 19769 invoked from network); 12 Feb 2021 22:19:19 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 12 Feb 2021 22:19:19 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 65FB41804CF for ; Fri, 12 Feb 2021 14:05:09 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=BAYES_20,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mercury.negativeion.net (mercury.negativeion.net [199.38.81.6]) by php-smtp4.php.net (Postfix) with ESMTP for ; Fri, 12 Feb 2021 14:05:08 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mercury.negativeion.net (Postfix) with ESMTP id A372820C675A94; Fri, 12 Feb 2021 17:05:08 -0500 (EST) Received: from mercury.negativeion.net ([127.0.0.1]) by localhost (mercury.negativeion.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l6966fWXjo4N; Fri, 12 Feb 2021 17:05:08 -0500 (EST) Received: from [10.0.1.101] (unknown [173.225.146.47]) by mercury.negativeion.net (Postfix) with ESMTPSA id DF1AF20C675A87; Fri, 12 Feb 2021 17:05:07 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\)) In-Reply-To: Date: Fri, 12 Feb 2021 16:05:07 -0600 Cc: internals@lists.php.net Content-Transfer-Encoding: quoted-printable Message-ID: References: To: Mark Randall X-Mailer: Apple Mail (2.3608.120.23.2.1) Subject: Re: [PHP-DEV] [RFC] Fibers From: aaron@trowski.com (Aaron Piotrowski) > On Feb 12, 2021, at 3:47 PM, Mark Randall wrote: >=20 > 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. >=20 > Removing the scheduler was likely a good plan, but pretty please = reconsider your future scope. >=20 > 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. >=20 > 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. >=20 > Mark Randall >=20 > --=20 > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php >=20 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=