Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80571
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me>
References: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me>
Date: Thu, 15 Jan 2015 10:59:07 -0600
Message-ID: <CAN=kQJdmdu1J-aMVRSfFh8_tGFDC+8WBs9k1Qjn9ke6ZA1VRVQ@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints v0.2
From: leverton@gmail.com (Matthew Leverton)

On Tue, Jan 13, 2015 at 6:16 PM, Andrea Faulds <ajf@ajf.me> wrote:
> I=E2=80=99ve made some quite significant changes to my Scalar Type Hints =
RFC, and bumped its version to 0.2.
>
> Here: https://wiki.php.net/rfc/scalar_type_hints
>
> This is a new thread because I=E2=80=99ve made a significant revision to =
the RFC, so it=E2=80=99d be sensible to separate discussion of the updated =
RFC from the v0.1 RFC.
>
> Please tell me your thoughts.
>
I don't like this at all. I'd prefer raising a new warning type (e.g.,
E_AUTOCAST) over this.

Does the voting system support instant-runoffs? If people could rate
their preferences of:

1) strict scalar types
2) weak scalar types (auto cast)
3) both - different syntaxes. e.g, (int) $foo vs int $foo
4) no scalar types

we could reach a compromised consensus without some building
Frankenstein. I really think having either basic strict or weak types
is far preferred to nothing. There are good arguments on both sides
... let the voters decide.

After that, additional RFCs could be created to address raising errors
on auto case, using declares to toggle behavior, etc - depending of
course on what was decided on prior vote.

--
Matthew Leverton