On Sat, May 7, 2016 at 9:31 AM, Tom Worster <f...@thefsb.org> wrote: > On 5/6/16 3:41 PM, Levi Morrison wrote: >> >> The [RFC for Nullable Types][1] is going to go into the voting phase >> soon. There have been a few changes to the RFC in the meantime: >> >> - More example for documentation's sake >> - The vote is now split into two parts: one for nullable parameter >> types and one for nullable return types. > > > The vote counting surprises me. Say, for the sake of argument, a > hypothetical nullable returns RFC were to pass with 2/3. After that a 2nd > hypothetical RFC for nullable parameters goes to vote. This 2nd RFC would > need 2/3 to pass. Your RFC defines the same two separate language changes as > two votes but one of them requires only a majority. > > Also, could you clarify in the RFC text how the voting works. For example, > is it the case that the entire nullable parameter vote is discarded if the > nullable return vote does not pass? > > Tom
Dmitry is the one who wanted the split vote, so I will defer the answer to him. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
