rfc:null_coalesce_equal_operator
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
rfc:null_coalesce_equal_operator [2016/03/09 17:03] – created midorikocak | rfc:null_coalesce_equal_operator [2019/01/22 10:36] (current) – Implemented nikic | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== PHP RFC: Null Coalesce Equal Operator ====== | + | ====== PHP RFC: Null Coalescing Assignment |
- | * Version: 0.9 | + | * Version: 0.1.0 |
- | * Date: 2016-03-09 | + | * Date: 2016-03-09 |
* Author: Midori Kocak, mtkocak@gmail.com | * Author: Midori Kocak, mtkocak@gmail.com | ||
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
+ | |||
===== Introduction ===== | ===== Introduction ===== | ||
- | This is a suggested template for PHP Request for Comments (RFCs). Change this template to suit your RFC. | + | Combined assignment operators have been around since 1970' |
- | Read https://wiki.php.net/ | + | |
- | + | ||
- | + | ||
- | Quoting [[http:// | + | |
- | + | ||
- | > PHP is and should remain: | + | |
- | > 1) a pragmatic | + | |
- | > 2) a loosely typed language | + | |
- | > 3) a language which caters to the skill-levels and platforms of a wide range of users | + | |
- | + | ||
- | Your RFC should move PHP forward following his vision. As [[http:// | + | |
- | large chunk of our userbase, and not something | + | |
- | extremely specialized edge cases [...] Make sure you think about the full context, the huge audience out there, the consequences | + | |
- | every new feature, and the scope of the goodness that those new features bring." | + | |
- | + | ||
- | ===== Introduction ===== | + | |
- | The elevator pitch for the RFC. The first paragraph in this section will be slightly larger | + | |
===== Proposal ===== | ===== Proposal ===== | ||
- | All the features and examples of the proposal. | ||
- | To [[http:// | + | Despite ''??'' |
- | for inclusion in one of the world' | + | |
- | Remember that the RFC contents should be easily reusable in the PHP Documentation. | + | <code php> |
+ | // The folloving lines are doing the same | ||
+ | $this-> | ||
+ | // Instead of repeating variables with long names, | ||
+ | $this-> | ||
+ | </ | ||
- | ===== Backward Incompatible Changes ===== | + | The value of right-hand parameter |
- | What breaks, and what is the justification for it? | + | |
===== Proposed PHP Version(s) ===== | ===== Proposed PHP Version(s) ===== | ||
- | List the proposed PHP versions that the feature will be included in. Use relative versions such as "next PHP 7.x" or "next PHP 7.x.y" | ||
- | ===== RFC Impact ===== | + | This proposed for the next PHP 7.x. |
- | ==== To SAPIs ==== | + | |
- | Describe | + | |
- | ==== To Existing Extensions | + | ===== Patches and Tests ===== |
- | Will existing extensions be affected? | + | |
- | ==== To Opcache ==== | + | A pull request |
- | It is necessary to develop RFC' | + | |
- | Please explain how you have verified your RFC's compatibility with opcache. | + | ===== Vote ===== |
- | ==== New Constants ==== | + | As this is a language change, a 2/3 majority is required. A straight Yes/No vote is being held. |
- | Describe any new constants so they can be accurately and comprehensively explained in the PHP documentation. | + | |
- | ==== php.ini Defaults ==== | + | Voting started at 2016/03/24 16:08 and will be closed at 2016/04/02. |
- | If there are any php.ini settings then list: | + | |
- | * hardcoded default values | + | |
- | * php.ini-development values | + | |
- | * php.ini-production values | + | |
- | ===== Open Issues ===== | + | <doodle title=" |
- | Make sure there are no open issues when the vote starts! | + | * Yes |
- | + | * No | |
- | ===== Unaffected PHP Functionality ===== | + | </doodle> |
- | List existing areas/ | + | |
- | + | ||
- | This helps avoid any ambiguity, shows that you have thought deeply about the RFC's impact, | + | |
- | + | ||
- | ===== Future Scope ===== | + | |
- | This sections details areas where the feature might be improved in future, but that are not currently proposed in this RFC. | + | |
- | + | ||
- | ===== Proposed Voting Choices ===== | + | |
- | Include these so readers know where you are heading and can discuss the proposed voting options. | + | |
- | + | ||
- | State whether this project requires a 2/3 or 50%+1 majority (see [[voting]]) | + | |
- | + | ||
- | ===== Patches and Tests ===== | + | |
- | Links to any external patches and tests go here. | + | |
- | + | ||
- | If there is no patch, make it clear who will create a patch, or whether a volunteer to help with implementation is needed. | + | |
- | + | ||
- | Make it clear if the patch is intended to be the final patch, or is just a prototype. | + | |
- | + | ||
- | ===== Implementation ===== | + | |
- | After the project is implemented, | + | |
- | - the version(s) it was merged to | + | |
- | - a link to the git commit(s) | + | |
- | - a link to the PHP manual entry for the feature | + | |
===== References ===== | ===== References ===== | ||
Links to external references, discussions or RFCs | Links to external references, discussions or RFCs | ||
+ | |||
+ | http:// | ||
===== Rejected Features ===== | ===== Rejected Features ===== | ||
Keep this updated with features that were discussed on the mail lists. | Keep this updated with features that were discussed on the mail lists. |
rfc/null_coalesce_equal_operator.1457542991.txt.gz · Last modified: 2017/09/22 13:28 (external edit)