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.
