rfc:fiber
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:fiber [2018/04/17 23:27] – lvht | rfc:fiber [2018/06/12 07:40] (current) – move back to discussion krakjoe | ||
---|---|---|---|
Line 81: | Line 81: | ||
=== Implementation Detail === | === Implementation Detail === | ||
- | In our simple implementation, | + | 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 116: | Line 107: | ||
===== Open Issues ===== | ===== Open Issues ===== | ||
- | < | + | < |
- | </ | + | Martin Schröder is working on this at https://github.com/fiberphp/fiber-ext/pull/30. |
- | + | ||
- | Fiber does not support yielding during the internal call. Calling Fiber:: | + | |
- | + | ||
- | < | + | |
- | + | ||
- | Offering methods like < | + | |
- | + | ||
- | < | + | |
- | + | ||
- | The Fiber:: | + | |
- | + | ||
- | < | + | |
- | Both Ruby's Fiber and Lua's coroutine using the **resume()** API to **init** and **resume** their coroutine. There is no need to offer a **dedicate init** API. | + | And here is the comparison. |
+ | ^Property^Stackless Fiber^Native Fiber^ | ||
+ | |1 Minimum Memory Usage|VM stack only (4 KB)|VM & C stack (4 KB + 4 KB)| | ||
+ | |2 Supported Architecturs|any platform|x86 at this time| | ||
+ | |3 Yield in Internal Function|unsupported|supported| | ||
+ | |4 Yield in Iterator|unsupported|supported| | ||
- | < | + | Stackless fiber use less memory and are not platform-dependend |
- | You will get a Fatal Error like | + | Native fibers are very platform-dependend (2) and use more memory because they do need to allocate a C call stack (1). While memory allocation will be done using mmap() it will still reserve virtual memory (can be problematic for a large number of fibers on 32 bit systems due to limited virtual memory addressing). The big advantage is that all kinds of internal function call (3 & 4) are supported without any changes to the existing codebase. |
- | Fatal error: Uncaught Error: Cannot call Fiber::yield out of Fiber | + | < |
- | < | + | And as a language feature, Fiber should only offer the essential API. User can implement these methods |
- | Introducing new keywords like await/emit does not offer any essential benefit but only cause BC impact. | + | < |
- | Both Ruby's Fiber and Lua's coroutine | + | Both Ruby's Fiber and Lua's coroutine |
===== Unaffected PHP Functionality ===== | ===== Unaffected PHP Functionality ===== | ||
Line 149: | Line 133: | ||
===== Future Scope ===== | ===== Future Scope ===== | ||
- | This sections details areas where the feature might be improved in future, but that are not currently proposed in this RFC. | ||
- | ===== Proposed Voting Choices ===== | + | Syntax like async/await can be implemented in the future, but it's out of the scope of this RFC. |
- | 2/3+1 voting majority | + | |
===== Patches and Tests ===== | ===== Patches and Tests ===== |
rfc/fiber.1524007632.txt.gz · Last modified: 2018/04/17 23:27 by lvht