RE: [PHP-DEV] [VOTE] Scalar Type Hints
| From: | Zeev Suraski | Date: | Sun, 08 Feb 2015 21:22:25 +0000 |
| Subject: | RE: [PHP-DEV] [VOTE] Scalar Type Hints | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-82177@lists.php.net to get a copy of this message | ||
> -----Original Message-----
> From: Matthew Leverton [mailto:leverton@gmail.com]
> Sent: Sunday, February 08, 2015 11:17 PM
> To: Zeev Suraski
> Cc: Jordi Boggiano; PHP internals
> Subject: Re: [PHP-DEV] [VOTE] Scalar Type Hints
>
> On Sun, Feb 8, 2015 at 1:48 PM, Zeev Suraski <zeev@zend.com> wrote:
> >
> > proposal everyone can rally behind, it very clearly failed. We didn't
> > have to wait for a vote by the way, it was clear from the discussion
> > on internals@.
> >
> Controversial RFCs are precisely the ones that SHOULD be voted on.
Not really. These should be avoided as much as possible.
> Policy states that 2/3s means consensus on core language changes. The
> current 63.5% isn't too far from that. Just curious, but do you have a
> different number in mind for this vote? 90%? 80%?
I'm well aware of it as I wrote that policy. The goal of the policy was to
prevent a situation where a temporary majority can introduce features into
the language that would later on be impossible to reverse. It's not by any
stretch a good mechanism to solve controversial votes, which again, should
ideally be avoided as much as possible. It's just that there isn't a better
mechanism.
Zeev