PHP 7.1: actually… No!September 15, 2016 —
Cet article est aussi disponible en français.
This is the 9th post in a series about PHP 7.1.
These past few days, I wrote about the new features we’ll soon get in PHP 7.1. That being said, during about one year of development, a great number of other ideas have been discussed, many other RFCs have been written.
Some of these RFCs went to the voting phase and have been rejected, others didn’t go that far in the process, some might have been canceled… Well, many ideas have been discussed, and I’ll try listing them all here.
First, here are some RFCs that have been rejected, but caught my eyes when I recently re-read their titles:
- Short closures
- Number Format Separator
- PHP Attributes
- Functional Interfaces
- Callable Types
- Union Types
- Typed Properties
- Precise Session Management
And now, here are other proposals that have been discussed, even if the corresponding RFCs didn’t go as far as the voting phase (I think) — which means they weren’t rejected, but didn’t pass either:
- Operator Overloading
token_get_all()flag to return consistent elements
- Adopt Code Of Conduct
- Make Libsodium a Core Extension
- Class Friendship
- Add HTTP/2 Support to the CLI Server
- Deprecations for PHP 7.1
- Callable constructors
- Short ternary Equal Operator
- Generic Types and Functions
- Anonymous Class Lexical Scope
- Intersection Types
$thisbeing null in instance methods
- Allow loading extensions by name
- Automatic CSRF Protection
- Third-party editing of RFCs
- Simple Annotations
- Separate overloaded operations when assigning
- Simple Cryptography Library
- Arrow Functions
- Revisit trailing commas in function arguments
- Trailing Commas In List Syntax
- Automatic SQL Injection Protection
- Allow default value in
Some of these were rather interesting… And even if the majority will not make a come back later, we can reasonably think a few will be re-discussed in the future!