HomeSectionsAboutMerch

« Strings/encoding is terribleStructs »

Under discussion

Array key casting

Auto-capture closure aka multi-line blocks

Better web sapi

Call site error or exception control

Chained comparison operators

Class method callable

Class scoping improvements

Closure self-reference

Consistent callables

Method overloading

Multiple return types

Non-extending code re-use

Standardise core library

Static class initialization

Strict mode and internal engine callbacks

Strings/encoding is terrible

Template string literals

Throws declarations

Tuple return declarations

Typedef callable signatures

Ideas that overcame their challenges

Briefer closure syntax

Co- and contra-variance

Referencing functions

Ternary right associative

Things that are probably moot

Consistent callables

Explicit defaults

Blank

General idea

Being able to specify subtypes of string and int, would be nice.

I wrote up an idea for an RFC here but am not going to pursue it until strings in PHP are less terrible.

Hurdles to overcome

Hurdle 1

Forecast

Notes

© PHP OpenDocs © Danack Edit page Edit content