Skip to content
Branch: master
Find file Copy path
Find file Copy path
1 contributor

Users who have contributed to this file

68 lines (34 sloc) 2.57 KB


There are some notes on PHP RFCs, why some were declined, and what others might need for them to be implemented.

The purpose of these documents is to avoid information from being lost and to try to avoid conversations needing to be repeated multiple times on PHP internals.

Things still being discussed


Class scoping improvements

Consistent callables


Explicit defaults


Method overloading

Named params

Standardise core library

Strings/encoding is terrible

Strong typing


Ternary right associative

Typedef callable signatures


These need to be summarised.


Ini settings - why app level settings are kind of okay, but library level ones are bad.

Null short-circuiting -

Pipe-operator -

Tuple returns

Type declarations type number = float | int;

Ideas that overcame their challenges

Co- and contra-variance

Briefer closure syntax

Union types


Please read the contributing guidelines before writing your 4,000 word novelella on why some RFC really should pass.


I reserve the right to be as opinionated as I feel like when commenting on RFCs; I'm not going to attempt to stay 100% neutral when talking about RFCs that I consider to be either dumb or bad for PHP.

You can’t perform that action at this time.