Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113478
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
In-Reply-To: <tencent_59E9CE5E741DCBCA30A8A218@qq.com>
Date: Thu, 11 Mar 2021 10:29:42 -0600
Content-Transfer-Encoding: quoted-printable
Message-ID: <EAB2C75D-64C3-4E2C-A797-4340AFDA4DC2@trowski.com>
References: <tencent_5E47DEBA2843CDD57E4DE795@qq.com>
 <CAPrKfG7Nh+QYdgoBYjsbmi1nyt736H9R--_4+-=8t1C--A8wmQ@mail.gmail.com>
 <tencent_59E9CE5E741DCBCA30A8A218@qq.com>
To: php internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] [VOTE] Fibers
From: aaron@trowski.com (Aaron Piotrowski)



> On Mar 11, 2021, at 7:56 AM, =E9=9F=A9=E5=A4=A9=E5=B3=B0 =
<rango@swoole.com> wrote:
>=20
> The RFC does not mention how an extension uses fiber.
>=20

Hi,

I forgot to address your point that the RFC does not mention how an =
extension uses fibers.

I did omit this from the RFC as I focused on the user API, as that is =
typically what PHP RFCs focus on, but this is an important question.

There is not an internal API to create fibers at this time. However, I =
planned to collaborate with other internals developers to add this API =
(and of course with feedback from swoole developers), so this will be a =
feature available to PHP extensions.

Aaron Piotrowski