Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75482
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 as permitted sender)
Message-ID: <53C401CC.6010107@gmail.com>
Date: Mon, 14 Jul 2014 17:14:04 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <08503591-EFC8-48E6-984E-FFC292C5EA5F@ajf.me> <alpine.DEB.2.10.1407141536380.4247@whisky.home.derickrethans.nl> <AF61F548-FADC-428F-B76F-1BB82C645D2C@ajf.me> <alpine.DEB.2.10.1407141552290.4247@whisky.home.derickrethans.nl> <53C3F70A.7010706@gmail.com> <3aa29e080d70c843713e19a952dfbad6@mail.gmail.com>
In-Reply-To: <3aa29e080d70c843713e19a952dfbad6@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------060602060108060008030407"
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hinting With Casts (re-opening)
From: rowan.collins@gmail.com (Rowan Collins)

--------------060602060108060008030407
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Zeev Suraski wrote (on 14/07/2014):
>> -----Original Message-----
>> From: Rowan Collins [mailto:rowan.collins@gmail.com]
>> Sent: Monday, July 14, 2014 6:28 PM
>> To: internals@lists.php.net
>> Subject: Re: [PHP-DEV] [RFC] Scalar Type Hinting With Casts (re-opening)
>>
>> Derick Rethans wrote (on 14/07/2014):
>>> A compromise by adding more inconsistencies.
>> The only way of not introducing some inconsistencies (or, to put it
> another
>> way, new features) is to use strict type hints
> Actually there's a pretty simple way that's not strict type hints:
>
> 5) Add type hints using existing syntax, which are casts;  Change casts
> (both existing and these new ones) to emit a new E_CAST in case of data
> loss or 'bogus' conversions.
>
> Zeev

That's not consistent with current behaviour. This does not perform a 
cast, it performs strict validation:

function foo(array $bar) { /* ... */ }
foo('123');

Also, I already mentioned it:

> Option 2 (or 3) could also be implemented by making *all* lossy casts 
> emit some kind of notice. 

The only *consistent* behaviour is strict validation, period. If you 
want that, use Hack; if you want some other kind of type hint, it has to 
introduce something new.

--------------060602060108060008030407--