This page gives an overview of the current RFCs for PHP.
To create a new RFC, see How To Create an RFC.
Note: An RFC is effectively “owned” by the person that created it. If you want to make changes, get permission from the creator. If no agreement can be found, the only course of action is to create a competing RFC. In this case, the old RFC page should be modified to become an intermediate page that points to all the competing RFC's.
A new page in this RFC namespace will automatically be loaded with an RFC template. Customize as needed.
This section is for RFCs that have been announced on the PHP “internals” mail list.
scalarpseudo-type for parameter and return types (Created: 2017-12-24)
This section is for early drafts of RFCs that have NOT been announced on the PHP “internals” mail list.
Order in these sections: Language changes first, library changes later.
objecttype-hint and return-type (Created: 2016-08-12)
pcntl_signalhandler (Created 2016-06-14)
nullin class names or namespaces. (Created 2015-02-18)
<=>(Created 2014-02-12, revived 2015-01-19)
zend_parse_parametersfail if a float value out of bounds, or NaN, is passed where an integer is expected. (Created 2014-09-22)
Closureclass to allow calling bound to an object without pre-binding
Note: Many RFCs in this list have been mass voted.
gettype()function (Created: 2016-06-25)
var_type()function (Created: 2016-06-26)
varin favor of
readonlyspecifier to make properties writeable within a class, but only readable from outside (Created 2014-10-24)
This section is for RFCs that have been deferred, obsoleted, or appear to have been abandoned. Sorry if your RFC is added here and you feel it is still active; please move it back to the appropriate section.
-Woption to turn on maximum error reporting, and a
-Qoption for no error reporting. (Created 2011/07/05)
usesyntax. (Created 2011/04/06)