Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102085
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.173 as permitted sender)
MIME-Version: 1.0
References: <76EBF900-3BE8-4B60-9422-880A9754FCC4@lvht.net>
 <0DDFDACA-6322-461C-9D57-215E8C7D9CD0@trowski.com> <E48AB5EE-9C59-4564-A2C3-B56B84E86367@lvht.net>
 <CANUQDCgv2_2ZXRUqD-gVNpfiDxFkX--GagBxQf_OkB3W8dH1NQ@mail.gmail.com>
 <CF7C97E4-8C35-4808-98EB-18D17E88AF87@lvht.net> <CD68F70A-731E-4B74-AC1C-8DBA910E56AB@lvht.net>
 <CANUQDCgMgvzUDkguVKVr561jPQiPStH1UYZGcO7ACZK4ikAL+A@mail.gmail.com>
 <60FDAEC8-02A4-4AAE-A5E3-4A119946BEB5@lvht.net> <CANUQDCgM6Vfh_5x_UghvtV-26xy5EeUVfQ9GyG_YAQ_GgTqU1Q@mail.gmail.com>
In-Reply-To: <CANUQDCgM6Vfh_5x_UghvtV-26xy5EeUVfQ9GyG_YAQ_GgTqU1Q@mail.gmail.com>
Date: Sun, 29 Apr 2018 09:27:17 +0000
Message-ID: <CAAfnsFW6vn_cr8cq=X7xdnqes5_DmuTxamNBRyjcOk9ULGzkww@mail.gmail.com>
To: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000828150056af958ea"
Subject: Re: [PHP-DEV] [RFC] Fiber support (again)
From: peterkokot@gmail.com (Peter Kokot)

--000000000000828150056af958ea
Content-Type: text/plain; charset="UTF-8"

Hello,

I've only briefly tested current implementation and from my point of view,
people new to the concept of coroutines, the async/await syntax might be
much more readable and understandable what is happening behind and why this
might be useful to have in the core. But yes, I'm sure there is a lot to
integrate and refactor in PHP for that matter. Complex things are never
simple...

I think the implementation should be rethought a bit more. Especially for
the future of asynchronous PHP in general.

If nothing else, maybe the RFC should also explain in more details why
introducing the static calling of the `Fiber::yield` instead of doing a bit
more complex integration (from C point of view) and much more readable and
understandable `async/await` syntax.

The latest JavaScript and [Hacklang](
https://docs.hhvm.com/hack/async/introduction) have this quite
understandable and readable solved, compared to Ruby's Fibers
implementation.

The RFC might also need to dive deeper into the benefits, and refactor the
current usage example or add some more links what is this chapter all about.

Thanks for all your work so far though. Awesome stuff nonetheless.

--000000000000828150056af958ea--