Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93106
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain thefsb.org designates 108.166.43.83 as permitted sender)
To: Levi Morrison <levim@php.net>, internals <internals@lists.php.net>,
 Dmitry Stogov <dmitry@zend.com>
References: <CAFMT4NoBqMrNSP_6J8nzA6E_+UChkjUz0jCvhXy_GE9RV3r2=Q@mail.gmail.com>
Message-ID: <572E0A60.4090506@thefsb.org>
Date: Sat, 7 May 2016 11:31:44 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0)
 Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAFMT4NoBqMrNSP_6J8nzA6E_+UChkjUz0jCvhXy_GE9RV3r2=Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [RFC] Pre-vote notice for Nullable Types
From: fsb@thefsb.org (Tom Worster)

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