rfc:internal_function_return_types

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
rfc:internal_function_return_types [2015/02/05 03:43] reezerfc:internal_function_return_types [2017/09/22 13:28] (current) – external edit 127.0.0.1
Line 16: Line 16:
 API testable, this could also makes extension-implemented frameworks/libraries control their API testable, this could also makes extension-implemented frameworks/libraries control their
 return types. return types.
 +
 +See: https://github.com/php/php-src/pull/1050/files#diff-3ea93da7d1026a9f53948a5d14b1f7bdR247 
 +
 +
  
 ===== Backward Incompatible Changes ===== ===== Backward Incompatible Changes =====
Line 47: Line 51:
  
 1. Should we raise E_CORE_ERROR when error detected, should we just ignore it with a warning? 1. Should we raise E_CORE_ERROR when error detected, should we just ignore it with a warning?
-2. Return Types RFC internally support Nullable Types, but user land not, this RFC also support that, + 
-   Should support it?+2. Return Types RFC internally support Nullable Types, but user land not, this RFC also support that, should support it?
  
 ===== Unaffected PHP Functionality ===== ===== Unaffected PHP Functionality =====
Line 62: Line 66:
 ===== Patches and Tests ===== ===== Patches and Tests =====
  
-Coming Soon+https://github.com/php/php-src/pull/1050
  
 ===== Implementation ===== ===== Implementation =====
rfc/internal_function_return_types.1423107810.txt.gz · Last modified: 2017/09/22 13:28 (external edit)