Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81809
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain devilix.net designates 209.85.218.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CABRjmp9a-ZfqWv3B4xh70LUEGFP4RpXgNwwYkRmnq9ST0y7CuQ@mail.gmail.com>
References: <CA+9eiLuueVvYgT-fhCvzBSxzoDioinpc5Eok5OQtGDBG1FZM=w@mail.gmail.com>
	<CAPwsocFD6sUEzo6uE4X0N2OF_N_eze5k+=f7Z+WyZHum7=MoeA@mail.gmail.com>
	<CABRjmp9a-ZfqWv3B4xh70LUEGFP4RpXgNwwYkRmnq9ST0y7CuQ@mail.gmail.com>
Date: Wed, 4 Feb 2015 13:15:16 +0200
Message-ID: <CAPhkiZy+q0wMyEHXPbWW+V-W+sLKHV9jKehggw-pS-j+PEXrPw@mail.gmail.com>
To: Florian Margaine <florian@margaine.com>
Cc: Leigh <leight@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] What do we need strict scalar type hints for?
From: narf@devilix.net (Andrey Andreev)

Hi,

On Wed, Feb 4, 2015 at 1:02 PM, Florian Margaine <florian@margaine.com> wro=
te:
> Hi Leigh,
>
> Le 4 f=C3=A9vr. 2015 11:50, "Leigh" <leight@gmail.com> a =C3=A9crit :
>>
>> What was wrong with:
>>
>> function x(int $y, string $z) { // strict
>> function x((int) $y, (string) $z) { // casting
>>
>> This was the best suggestion I've seen that covers the requirements of
>> both camps, and is still very clear how data is going to be handled.
>>
>> Authors who want their APIs to adhered to strictly can do that,
>> authors who want to accept anything and have it end up as their
>> desired type can do that too.
>
> Because it is then the callee who decides, not the caller, whether or not
> he wants strict typing.
>

... and apparently, this is the root of all evil. :)

I am baffled by how the two-syntaxes suggestion is always so easily
dismissed by that argument. I'd argue that most people who support the
current proposal don't fully understand what declare(strict_type=3D1)
really does. As I've previously said - putting the caller in control
(and really the caller, not in a per-file context) makes it a
debugging tool, not support for strict typing.

Cheers,
Andrey.