Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83751 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72493 invoked from network); 25 Feb 2015 09:21:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Feb 2015 09:21:56 -0000 Authentication-Results: pb1.pair.com header.from=pajousek@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pajousek@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.182 as permitted sender) X-PHP-List-Original-Sender: pajousek@gmail.com X-Host-Fingerprint: 209.85.216.182 mail-qc0-f182.google.com Received: from [209.85.216.182] ([209.85.216.182:37005] helo=mail-qc0-f182.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3B/22-62407-1349DE45 for ; Wed, 25 Feb 2015 04:21:55 -0500 Received: by qcrw7 with SMTP id w7so1915278qcr.4 for ; Wed, 25 Feb 2015 01:21:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YHzUFFfd2GoC4e5vadMIRmRul8yHtGbdnKlk3dy9C1Y=; b=LKwSxdru1mFkCyCrb7krM1c80KyP28ReEWWbyLjCQwbjY0Q767xvn4/1aP2VXmJ1+b /wd3vobo2tbPwqqnmFBEMm4OUyEUK1rAg/Smy2MNvAi1eIi45gaLo9ZIzOTVdnCOtvbb QnQ5tGFq0eRheMGso75ytIuNgdJbDOqIPA9myRNIn0wQtqfo8qdHFxe5POb7xUQoSNX3 bCHvAyYaMAgZ3g3EKJVlDcdf9GL7xSCszMM+/7aK5aVXz6/WaYcrdTejSuyVjz2gbDw/ E261HPHxGi/66BfN4idd91Em98TDCIA9FRB9HLvEQsjIz0NMrro3o6pV0HSClsUd4yy5 yMVQ== MIME-Version: 1.0 X-Received: by 10.140.38.197 with SMTP id t63mr4616548qgt.61.1424856111215; Wed, 25 Feb 2015 01:21:51 -0800 (PST) Received: by 10.96.160.99 with HTTP; Wed, 25 Feb 2015 01:21:51 -0800 (PST) In-Reply-To: <0aa4f2f9eedf3c66af3463d42a9d4645@mail.gmail.com> References: <0aa4f2f9eedf3c66af3463d42a9d4645@mail.gmail.com> Date: Wed, 25 Feb 2015 10:21:51 +0100 Message-ID: To: Zeev Suraski Cc: Leigh , Albert Casademont Filella , Benjamin Eberlei , PHP Internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] The Game Theory of Scalar Type Hint Voting From: pajousek@gmail.com (=?UTF-8?Q?Pavel_Kou=C5=99il?=) On Wed, Feb 25, 2015 at 10:09 AM, Zeev Suraski wrote: >> -----Original Message----> From: Leigh [mailto:leight@gmail.com] >> Sent: Tuesday, February 24, 2015 2:56 PM >> To: Albert Casademont Filella >> Cc: Benjamin Eberlei; PHP Internals >> Subject: Re: [PHP-DEV] The Game Theory of Scalar Type Hint Voting >> >> On 23 February 2015 at 21:15, Albert Casademont Filella >> wrote: >> > I like it! That's what I proposed to Anthony (and Andrea before) >> > before Zeev presented their alternative, to held a double vote on the >> > strict vs weak feature. It was not met with much enthusiasm, hope they >> > change their minds with your proposal! >> >> Except a dual vote is probably not going to work in favour of strict vs. >> weak. >> >> Why would anyone who wants purely strict vote for "Yes (strict)", when >> they >> know that "Yes (weak)" is going to have the majority. It boils down to >> voting >> Yes for something you don't want. I don't think it will convert votes at >> all. >> _If_ I wanted _strict only_ and I was presented with "Yes (strict)", "Yes >> (weak)", and "No" and could see the weak vote winning by a clear margin, I >> would vote No. > > Leigh, > > There isn't a weak-only proposal on the table. There's the original one > (dual mode) and the coercive one. Both have both strict and dynamic > elements in them. > I think that what Anthony proposed about a week or so ago, of having both > votes, and if both pass 2/3 - have another vote to choose between them > (where a simple majority wins) - makes the most sense in this uncharted > territory. > I think that opening the votes at the same time is probably a good idea. > > Zeev > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > Well, one thing that would help apart from opening them at the same time is also making the results not public until the voting ends (but I'm not sure if this isn't prohibited by the RFC voting process guidelines). Regards Pavel Kouril