Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:93111 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 8438 invoked from network); 8 May 2016 13:54:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 May 2016 13:54:21 -0000 Authentication-Results: pb1.pair.com header.from=fsb@thefsb.org; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=fsb@thefsb.org; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain thefsb.org designates 173.203.187.91 as permitted sender) X-PHP-List-Original-Sender: fsb@thefsb.org X-Host-Fingerprint: 173.203.187.91 smtp91.iad3a.emailsrvr.com Linux 2.6 Received: from [173.203.187.91] ([173.203.187.91:41253] helo=smtp91.iad3a.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7E/30-04420-B054F275 for ; Sun, 08 May 2016 09:54:20 -0400 Received: from smtp4.relay.iad3a.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp4.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id BEB0F28079A; Sun, 8 May 2016 09:54:16 -0400 (EDT) X-Auth-ID: fsb@thefsb.org Received: by smtp4.relay.iad3a.emailsrvr.com (Authenticated sender: fsb-AT-thefsb.org) with ESMTPSA id DB157280795; Sun, 8 May 2016 09:54:14 -0400 (EDT) X-Sender-Id: fsb@thefsb.org Received: from [10.0.1.2] (c-66-30-62-12.hsd1.ma.comcast.net [66.30.62.12]) (using TLSv1 with cipher DES-CBC3-SHA) by 0.0.0.0:465 (trex/5.5.4); Sun, 08 May 2016 09:54:16 -0400 User-Agent: Microsoft-MacOutlook/14.6.3.160329 Date: Sun, 08 May 2016 09:54:11 -0400 To: Nikita Popov CC: Levi Morrison , internals , Dmitry Stogov Message-ID: Thread-Topic: [PHP-DEV] Re: [RFC] Pre-vote notice for Nullable Types References: <572E0A60.4090506@thefsb.org> In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: 7bit Subject: Re: [PHP-DEV] Re: [RFC] Pre-vote notice for Nullable Types From: fsb@thefsb.org (Tom Worster) On 5/7/16, 1:19 PM, "Nikita Popov" wrote: >This RFC has one primary vote and one secondary vote. The primary vote >determines whether we want to add nullable types to our type system. The >secondary vote decides how precisely this will happen, in this instance >deciding whether nullable types will be restricted to return types only >or not. This is a standard voting layout, with precedent in a number of >other RFCs. > >The reason why the second vote must use a 1/2 majority is symmetry. You, >as somebody who does not like nullable parameter types, argue from a >perspective of one 2/3 majority RFC for introducing nullable returns and >another 2/3 majority RFC for introducing nullable params. I, as somebody >who thinks supporting this syntax only for returns is wildly >inconsistent, will argue from a perspective of a 2/3 majority RFC for >introducing nullable *types* and another 2/3 majority RFC for restricting >them to return types only. Depending on the perspective this would >require either a 2/3 majority, or a 1/3 "majority" for unrestricted >nullable types. Using a 1/2 majority vote ensures that there is no bias >for either choice. The explanation is very clear. Thank you. Tom (Btw, I don't disagree about the inconsistency you mentioned. But I don't think it's a wild inconsistency, rather a justified one, given our context.)