rfc:internal_function_return_types
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
rfc:internal_function_return_types [2015/02/05 03:44] – reeze | rfc:internal_function_return_types [2015/02/05 04:23] – reeze | ||
---|---|---|---|
Line 16: | Line 16: | ||
API testable, this could also makes extension-implemented frameworks/ | API testable, this could also makes extension-implemented frameworks/ | ||
return types. | return types. | ||
+ | |||
+ | See: https:// | ||
+ | |||
+ | |||
===== 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, | + | |
- | | + | 2. Return Types RFC internally support Nullable Types, but user land not, this RFC also support that, should |
===== Unaffected PHP Functionality ===== | ===== Unaffected PHP Functionality ===== |
rfc/internal_function_return_types.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1