Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:88133
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.182 as permitted sender)
To: internals@lists.php.net
References: <55E4B9AA.9060906@dasprids.de> <09.54.59944.CD76CE55@pb1.pair.com>
Message-ID: <55F17500.6080806@gmail.com>
Date: Thu, 10 Sep 2015 13:18:08 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <09.54.59944.CD76CE55@pb1.pair.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Generic classes and methods RFC
From: rowan.collins@gmail.com (Rowan Collins)

Andrea Faulds wrote on 06/09/2015 17:20:
> If we hadn't seen the class declaration at the top which makes 
> `KeyType` and `ValueType` be type parameters, we might not realise 
> they weren't ordinary classes or interfaces when we looked at 
> `__construct`. The -Type suffix you've used helps a little, but that's 
> a convention, and isn't guaranteed to be used. Also, in some existing 
> projects, there might be classes with that suffix. 

As I understand it, the convention in a lot of languages is that type 
parameters are a single upper-case letter. I'm not sure if any enforce 
this restriction, though, and a sigil does seem more flexible and readable.

Regards,
-- 
Rowan Collins
[IMSoP]