rfc:fcc_in_const_expr
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:fcc_in_const_expr [2025/01/07 14:15] – timwolla | rfc:fcc_in_const_expr [2025/01/22 14:31] (current) – Set to under discussion edorian | ||
---|---|---|---|
Line 3: | Line 3: | ||
* Date: 2025-01-07 | * Date: 2025-01-07 | ||
* Author: Tim Düsterhus (tim@tideways-gmbh.com), | * Author: Tim Düsterhus (tim@tideways-gmbh.com), | ||
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
Line 29: | Line 29: | ||
==== Scoping ==== | ==== Scoping ==== | ||
- | As with other constant-expressions, | + | As with other constant-expressions, |
- | All the features and examples of the proposal. This means that FCC in property default values //may// reference < | + | |
==== Examples ==== | ==== Examples ==== | ||
Line 84: | Line 83: | ||
==== To Opcache ==== | ==== To Opcache ==== | ||
- | tbd | + | The current implementation uses a special AST structure to cache the resolved function for consistent behavior of the global function fallback. To correctly cache this AST structure, Opcache changes are required. The PR passes all tests both with and without JIT enabled. |
==== New Constants ==== | ==== New Constants ==== |
rfc/fcc_in_const_expr.1736259312.txt.gz · Last modified: 2025/01/07 14:15 by timwolla