Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81961
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.200 as permitted sender)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-ID: <8703B53E-2C4A-4AC6-95C4-D4F19C6D5221@ajf.me>
Date: Thu, 5 Feb 2015 20:14:48 +0000
To: PHP Internals <internals@lists.php.net>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Subject: [VOTE] Scalar Type Hints
From: ajf@ajf.me (Andrea Faulds)

Good evening,

At long last, I=E2=80=99m going to put the RFC to a vote. It=E2=80=99s =
been long enough - I don=E2=80=99t think there needs to be, or will be, =
much further discussion.

I=E2=80=99d like to make sure that everyone voting understands the RFC =
fully. Please read the RFC in full: the details are important. And if  =
anyone has any questions or uncertainties, please ask them before =
voting. I am very happy to answer them.

I would urge everyone who wants type hints to vote for this RFC. It is =
not a perfect solution, but there can be no perfect solution to this =
issue. However, I think it is better than most of the alternatives =
suggested thus far - see the rationale section, and previous =
discussions. Crucially, this RFC would keep PHP a weakly-typed language, =
and not force either strict typing, nor weak typing, on anyone who does =
not want it. It would allow the addition of type hints to existing =
codebases. It would not create a situation where userland functions are =
strict yet internal functions are not, because the strict mode affects =
both. I=E2=80=99ve tested the implementation myself on my own code, and =
it worked well, providing benefits other proposals would not have given =
(see my previous post about my experiences).

Voting starts today (2015-02-05) and ends in two weeks=E2=80=99 time =
(2015-02-19). In addition to the vote on the main RFC, there is also a =
vote on the type aliases issue, and a vote to reserve the type names for =
future RFCs=E2=80=99 sake if this RFC fails.

The RFC can be found here, and it contains a voting widget: =
https://wiki.php.net/rfc/scalar_type_hints

Thank you for your time.

--
Andrea Faulds
http://ajf.me/