> Hello again everyone! > > Based upon feedback both on this list and elsewhere, I’ve decided to remove > the FiberScheduler API from the fiber proposal. > > The FiberScheduler API greatly increased the complexity of the implementation > and the potential for edge cases that would need to be handled and > maintained. The intent of including the FiberScheduler API as part of the > proposed implementation was to require usage of fibers to be interoperable > between various libraries. However, this was perhaps over-reaching, and the > core should only provide the most fundamental tools for fibers. > > The Fiber API proposed now resembles that of Ruby and other languages > providing a fiber API. The revised RFC now proposes only a minimal API > required for fibers – no more, no less. I believe this minimal, simplified > API should resolve any concerns raised about adding the fiber API to core. > > 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. > > As before, amphp v3 (https://github.com/amphp/amp/tree/v3) and > trowski/react-fiber (https://github.com/trowski/react-fiber) provide > real-world examples of how fibers can be used in addition to the examples in > the RFC. >
Hi all! Since there has not been much feedback lately on the Fiber RFC, I wanted to notify everyone that I intend to start voting on the RFC next week Monday. If you have any questions or concerns, please do raise them now, as it’s always more difficult to address these once voting has started. I feel this feature deserves a lot of time to merge and test if it is to be included in 8.1, so I’d like to move forward soon. Cheers, Aaron Piotrowski -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
