Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81107
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
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
In-Reply-To: <54C46DB4.2090406@gmail.com>
Date: Sun, 25 Jan 2015 04:19:49 +0000
Cc: PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <4430AC4E-3D85-4672-868B-5A1E939FAE85@ajf.me>
References: <41D5BB0B-73AF-488E-968D-90B2878E3178@ajf.me> <90B1885A-E767-484E-8F38-A791E8A3FE9B@ajf.me> <54C46DB4.2090406@gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints
From: ajf@ajf.me (Andrea Faulds)

Hey Stas,

> On 25 Jan 2015, at 04:14, Stanislav Malyshev <smalyshev@gmail.com> =
wrote:
>=20
> Hi!
>=20
>> going to a vote. That said, I do lean towards always strict, given
>> you can usually ensure your return type=E2=80=99s correct.
>=20
> Wait, so we would have two modes, strict and non-strict, but also in
> non-strict mode, return types still will be strict? Yay, consistency!

Yes, it would have that inconsistency, so there=E2=80=99s also the other =
possibility of being weak for return types in weak mode.

Thing is, I haven=E2=80=99t seen (so far) anyone who seems to think =
return types should be converted. We don=E2=80=99t do this for internal =
functions (to be fair, there=E2=80=99s no need, C is statically-typed). =
Them being strict would follow the robustness principle, too: =E2=80=9Cbe =
conservative in what you send, be liberal in what you accept=E2=80=9D.

On the other hand, it may not be terribly fitting with =E2=80=9CPHP=E2=80=99=
s weakly-typed nature=E2=80=9D.

It=E2=80=99s hard to say.

--
Andrea Faulds
http://ajf.me/