Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61171
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.213.42 cause and error)
Message-ID: <4FFEFD81.6020404@lerdorf.com>
Date: Thu, 12 Jul 2012 09:38:25 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: Stas Malyshev <smalyshev@sugarcrm.com>
CC: Anthony Ferrara <ircmaxell@gmail.com>, 
 "internals@lists.php.net" <internals@lists.php.net>
References: <CAAyV7nGwONAwPRRYLKswJtR-1RsrhQc5yS+dVuyZr1BHBW_NBA@mail.gmail.com> <4FFEFBB3.7090507@sugarcrm.com>
In-Reply-To: <4FFEFBB3.7090507@sugarcrm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Iterable Type Hint
From: rasmus@lerdorf.com (Rasmus Lerdorf)

On 07/12/2012 09:30 AM, Stas Malyshev wrote:
> Hi!
> 
>> Would it be worth while adding a new type hint that checks for this
>> condition? I'd propose Iterable:
> 
> I see more and more multiplication of weird ad-hoc type checks. First we
> had "callable", now "traversable", then we invent more and more weird
> functional types with complex logic. I don't like this development at
> all. It's ad-hoc introducing of half-baked, unstandartized, undesigned
> strict typing. Strict typing is not a good idea for PHP, and weird
> strict typing based on complex conditions hidden from the user is even
> worse IMO.

For non-interchangeable types it is already strict by definition. I
don't see a problem with type hints that make life easier on both the
caller (by generating better error messages) and the callee (by having
to write less boilerplate type verification code).

You may have a point on the ad-hoc nature of it and that we need to do
it once and for all in a more organized fashion, but the basic premise
looks ok to me.

-Rasmus