Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61182
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain nebm.ist.utl.pt from 193.136.128.21 cause and error)
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: internals@lists.php.net
References: <CAAyV7nGwONAwPRRYLKswJtR-1RsrhQc5yS+dVuyZr1BHBW_NBA@mail.gmail.com> <4FFEFBB3.7090507@sugarcrm.com>
Date: Thu, 12 Jul 2012 19:40:31 +0200
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Organization: =?utf-8?Q?N=C3=BAcleo_de_Eng=2E_Biom=C3=A9di?=
 =?utf-8?Q?ca_do_I=2ES=2ET=2E?=
Message-ID: <op.whcgptelidpuyk@damnation>
In-Reply-To: <4FFEFBB3.7090507@sugarcrm.com>
User-Agent: Opera Mail/12.50 (Linux)
Subject: Re: [PHP-DEV] Iterable Type Hint
From: glopes@nebm.ist.utl.pt ("Gustavo Lopes")

Em Thu, 12 Jul 2012 18:30:43 +0200, Stas Malyshev <smalyshev@sugarcrm.com>  
escreveu:

>> 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.

I agree with everything Stas said.

Additionally, while "callable" has a problem that "iterable" wouldn't have  
-- namely, whether something is callable is context sensitive* -- its  
implementation was accompanied by a homogenization of callable types  
(e.g., you can now do $a = $func = ['A', 'foo']; $a()). Traversable types  
are by no means interchangeable. In fact the only thing they have in  
common is that can be passed to foreach. On everything else, they're  
different. It makes to sense to a pseudo-type for two entities that all  
they have in common is that one property.


* Example:

class A {
	public static function foo(callable $r) {
		B::foo($r);
	}
	private static function test() {}
}
class B {
	public static function foo(callable $r) {}
}

A::foo(['A', 'test']);


-- 
Gustavo Lopes