Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71365
Return-Path: <cryptocompress@googlemail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 56846 invoked from network); 20 Jan 2014 22:10:11 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 20 Jan 2014 22:10:11 -0000
Authentication-Results: pb1.pair.com header.from=cryptocompress@googlemail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=cryptocompress@googlemail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.214.52 as permitted sender)
X-PHP-List-Original-Sender: cryptocompress@googlemail.com
X-Host-Fingerprint: 209.85.214.52 mail-bk0-f52.google.com  
Received: from [209.85.214.52] ([209.85.214.52:53198] helo=mail-bk0-f52.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 17/CE-02192-1CE9DD25 for <internals@lists.php.net>; Mon, 20 Jan 2014 17:10:10 -0500
Received: by mail-bk0-f52.google.com with SMTP id e11so1737829bkh.39
        for <internals@lists.php.net>; Mon, 20 Jan 2014 14:10:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlemail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        bh=VCELIMhAYYtkfNPdoAeNN7oWjDvVcgsZuPRode77KWY=;
        b=FZ9w7BHt272kWQh6DfIonhXLZl3eCwEbmN6wkvZ8i8yyg+jflqcWJ3/9fTopkayBML
         a2siVljRohwymDVij2hwLDLz5H3WfQ/q4/mc6qw1vxqJegldY3xNj3nYz6FDOAR6nKzy
         ZB/T9CruEOdm+OtB5+XM1iYUzD2ikkorCQXqwjXj5fz+Q7XBNPROHWMnlos8ygYzEnzL
         q66OXazrmKqWRtQG/2k480J9Y318piQqBXuT2fLyQ7KTpPR6wIcVQul+S0n9yHjrfDIT
         3hx15W/uqsWMB4bfuut6mxiLYf5V5+R3cUe2Gw/wQJ66J12v0owmVzJwA42vEFpCt8b6
         HysA==
X-Received: by 10.205.20.1 with SMTP id qm1mr45136bkb.80.1390255806939;
        Mon, 20 Jan 2014 14:10:06 -0800 (PST)
Received: from [192.168.1.115] (mnch-5d85485c.pool.mediaWays.net. [93.133.72.92])
        by mx.google.com with ESMTPSA id jv7sm2123447bkb.6.2014.01.20.14.10.05
        for <internals@lists.php.net>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Mon, 20 Jan 2014 14:10:05 -0800 (PST)
Message-ID: <52DD9EAF.90805@googlemail.com>
Date: Mon, 20 Jan 2014 23:09:51 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: PHP Developers Mailing List <internals@lists.php.net>
References: <CABDNdAGCH5i9-=4Ys1CXeNaGWGmX=mkTiq0b7BbUKtBPdQ9XVg@mail.gmail.com>	<CAFRKLUNL_4Kyxe3HRs70Xgsiy4pKo0rsEnEyPCT80B7W20U6jQ@mail.gmail.com>	<CAGAGxba2U0_pK0kXx-+N=34UJiLUd9ev-TNf=R+jMzzVRGzW3w@mail.gmail.com>	<CAL+t6cE5KxpfSny3pNyW1s-0v00ocC7g=ee6AKcxo1bYoBrKeg@mail.gmail.com>	<CABDNdAG60oWEkjRegE4qc6WE_KcJvv=uqtVPRzihm-42PRcgyg@mail.gmail.com>	<52DCA3E7.80602@lerdorf.com>	<52DCED71.3020207@pthreads.org>	<006301cf15f5$22f8df60$68ea9e20$@tutteli.ch>	<CABDNdAEbzu+J-GQ73_2ra-tuX3aTGDPxue4_gCXu3iOnQgGpvg@mail.gmail.com>	<CAESVnVp8wjeCXKA6g=0mNzj3E0sR2FKtNRrzL7zPgsEk71Em7w@mail.gmail.com>	<52DD77E8.8000800@ajf.me>	<CAAR7rTEKspoDFQNy8zz68v4GNN-AGUVLdp_AhJwOaQwzRQUZhA@mail.gmail.com>	<CAESVnVreKN6paTPKf2bjDW9hORQ0op39u0_9FNGGwSfLAOc76g@mail.gmail.com>	<52DD8E98.3010606@sugarcrm.com>	<CAESVnVpMxfTbF44Dk7nNEfF4gFAMrfFJVrqNfAZpR-1CcrWMVA@mail.gmail.com>	<52DD94AE.6030705@sugarcrm.com> <CAESVnVrmPyFiz=4hjOMaZCJJ3GNscGuOpp4tSnRPJ-bdpUrc6Q@mail.gmail.com>
In-Reply-To: <CAESVnVrmPyFiz=4hjOMaZCJJ3GNscGuOpp4tSnRPJ-bdpUrc6Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Introducing "Array Of" RFC
From: cryptocompress@googlemail.com (Crypto Compress)

Yeah, ability to check on input and to blend syntax are the reasons for 
generics to came up in this discussion. *whirl* *whirl*
Even generics can solve this, it's not part of this RFC. Nor is this RFC 
somehow prevent generics. They can coexist:

Dictionary<int, string>[] foo
Array<Dictionary<int, string>> foo


Consider to vote "no" and stop derailing this RFC.