rfc:fiber
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:fiber [2018/02/10 15:47] – lvht | rfc:fiber [2018/04/17 23:51] – lvht | ||
---|---|---|---|
Line 2: | Line 2: | ||
* Version: 0.1 | * Version: 0.1 | ||
* Date: 2017-09-13 | * Date: 2017-09-13 | ||
- | * Author: Haitao Lv, i@lvht.net | + | * Author: Haitao Lv<i@lvht.net>, Dmitry Stogov< |
* Status: Under Discussion | * Status: Under Discussion | ||
* First Published at: http:// | * First Published at: http:// | ||
Line 16: | Line 16: | ||
===== Proposal ===== | ===== Proposal ===== | ||
==== Why not make it as a Extension? ==== | ==== Why not make it as a Extension? ==== | ||
+ | Fiber is a major language feature, that allows significant benefits for asynchronous frameworks. Providing it as an optional extension, just doesn' | ||
+ | |||
==== Implementation ==== | ==== Implementation ==== | ||
+ | === Proposed API === | ||
<code php> | <code php> | ||
final class Fiber { | final class Fiber { | ||
Line 25: | Line 28: | ||
public const STATUS_DEAD | public const STATUS_DEAD | ||
+ | /** | ||
+ | * @param callable $callable any php callable to be paused | ||
+ | * @param int $stack_size fiber stack init size | ||
+ | */ | ||
public function __construct(callable $callable = null, int stack_size = null) {} | public function __construct(callable $callable = null, int stack_size = null) {} | ||
+ | /** | ||
+ | * pause the current fiber and ~return~ the $arg1 | ||
+ | * as the Fiber:: | ||
+ | */ | ||
public static function yield($arg1) {} | public static function yield($arg1) {} | ||
+ | | ||
+ | /** | ||
+ | * Start or resume a fiber. | ||
+ | | ||
+ | * If the fiber is not started, call resume will init | ||
+ | * the $callable with all args. | ||
+ | * | ||
+ | * If the fiber is paused, call resume will send the first arg | ||
+ | * as the last Fiber:: | ||
+ | */ | ||
public function resume($arg1...) {} | public function resume($arg1...) {} | ||
+ | | ||
+ | /** | ||
+ | * Throw an exception into the fiber. | ||
+ | | ||
+ | * You code can use try/catch to process error in the | ||
+ | * top level function call. Some framework make heavy | ||
+ | * usage of this feature. | ||
+ | */ | ||
public function throw(Throwable $e) {} | public function throw(Throwable $e) {} | ||
- | |||
- | /** @throws \UnexpectedValueException */ | ||
- | public function __wakeup(): void {} | ||
- | |||
- | /** @throws \Error */ | ||
- | private function __clone() {} | ||
} | } | ||
</ | </ | ||
+ | === Usage Demo === | ||
<code php> | <code php> | ||
function sub1() | function sub1() | ||
Line 55: | Line 79: | ||
echo $fiber-> | echo $fiber-> | ||
</ | </ | ||
+ | |||
+ | === Implementation Detail === | ||
+ | In our simple implementation, | ||
+ | |||
+ | Martin Schröder has another implementation at https:// | ||
+ | |||
+ | |||
+ | ^Property^Martin' | ||
+ | |Minimum Memory Usage|VM stack only (4 KB)|VM & C stack (4 KB + 4 KB)| | ||
+ | |Supported Architecturs|any platform supported by compiler|only x86 systems at this time| | ||
+ | |Yield in Internal Function|unsupported|supported| | ||
+ | |Yield in Iterator|unsupported|supported| | ||
===== Backward Incompatible Changes ===== | ===== Backward Incompatible Changes ===== | ||
Line 80: | Line 116: | ||
===== Open Issues ===== | ===== Open Issues ===== | ||
- | < | + | < |
</ | </ | ||
- | Fiber does not support yielding during the internal call. Calling Fiber:: | + | Calling Fiber:: |
- | However, avoiding yield in the internal still make sense and useful | + | |
- | < | + | < |
- | Offering methods like Fiber:: | + | Offering methods like **Fiber:: |
- | < | + | And as a language feature, Fiber should only offer the essential API and let other works to the userland code. |
- | The Fiber::throw(Exception $exception) has been implemented. | + | < |
- | < | + | Both Ruby' |
- | Both Ruby's Fiber and Lua's coroutine using one **resume** API to init and resume their coroutine. There is no need to offer a dedicate **init** API. | + | < |
- | < | + | Introducing new keywords like await/emit does not offer any essential benefit but only cause BC impact. |
- | You will get a Fatal Error like | + | Both Ruby's Fiber and Lua's coroutine use method to pause and resume their coroutine. |
- | + | ||
- | Fatal error: Uncaught Error: Cannot call Fiber:: | + | |
- | + | ||
- | < | + | |
- | + | ||
- | Introducing new keywords like await/emit does not offer any essential benefit but cause BC impact. | + | |
- | + | ||
- | Both Ruby's Fiber and Lua's coroutine use method to pause and resume their coroutine. There is no need to introduce new keyword. | + | |
===== Unaffected PHP Functionality ===== | ===== Unaffected PHP Functionality ===== | ||
Line 117: | Line 144: | ||
===== Proposed Voting Choices ===== | ===== Proposed Voting Choices ===== | ||
- | Simple 50%+1 majority | + | 2/3+1 voting |
===== Patches and Tests ===== | ===== Patches and Tests ===== | ||
- | coming soon. Current developing at https:// | + | * https:// |
- | + | * < | |
- | * < | + | * < |
+ | * < | ||
+ | * < | ||
===== Implementation ===== | ===== Implementation ===== | ||
Line 137: | Line 166: | ||
===== Rejected Features ===== | ===== Rejected Features ===== | ||
- | Keep this updated with features that were discussed on the mail lists. |
rfc/fiber.txt · Last modified: 2018/06/12 07:40 by krakjoe