This RFC prevents the use of the following words to be used as a class, interface or trait name:
int
float
bool
string
true
, false
null
This RFC does not fully reserve them as keywords; it only prohibits their usage as class, interface and trait names. It also prevents them from being used in namespaces.
I have chosen to not reserve integer
, double
and boolean
out of interest of proposing the smallest useful subset. Another RFC could reserve these aliases in the future.
Reserving these words in PHP 7 would allow for another RFC to add scalar types in a minor release such as PHP 7.1 (assuming they make no backwards compatibility breaks). Without reserving them now a future RFC would only be able to target major PHP versions such as version 8 since they would break backwards compatibility.
Given that PHP has primitive types such as int, float, string and null it does not make sense for them to exist as classes, or if they do they should be provided by PHP itself.
This breaks any and all cases where these new reserved words are used in class, interface or trait names. It does not break any usages as function or method names or as class constants.
This RFC does not change the way our current parameter and return type hints work. Support for these new reserved words as types for parameters or return types is beyond the scope of this RFC.
Potentially future RFCs could:
integer
, double
and boolean
int|false
numeric
, mixed
or scalar
The vote will be a simple “yes” or “no”: do you vote in favor of reserving these type names?
This RFC requires at least two thirds of the votes to be “yes” to pass.
There is currently no implementation.
int
, integer
, float
, double
, bool
, boolean
, string
, true
, false
, null
integer
, double
and boolean