Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71202
Return-Path: <iam.asm89@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 88967 invoked from network); 17 Jan 2014 08:00:28 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 17 Jan 2014 08:00:28 -0000
Authentication-Results: pb1.pair.com header.from=iam.asm89@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=iam.asm89@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.53 as permitted sender)
X-PHP-List-Original-Sender: iam.asm89@gmail.com
X-Host-Fingerprint: 209.85.219.53 mail-oa0-f53.google.com  
Received: from [209.85.219.53] ([209.85.219.53:55050] helo=mail-oa0-f53.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 28/E1-04749-B13E8D25 for <internals@lists.php.net>; Fri, 17 Jan 2014 03:00:28 -0500
Received: by mail-oa0-f53.google.com with SMTP id m1so2991200oag.12
        for <internals@lists.php.net>; Fri, 17 Jan 2014 00:00:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=XVhf7hI1XzXZ7zOSeebmDlKjtXVCjOs3fTKBwutwimw=;
        b=GrmsK/thtQByxtBjwdyHMwadeLJKv+N+9Fq6PGKvogh2UkV0PRpSrPGA/MZpMfx1sv
         Ad5pV7tO5/EKVuO9QqHl0x8TMaOZdhoXvDSV4H9okMKgTHmMLsPrRkKmki8gaGJ619R0
         ZGQ3cbmR5HgtBEq89w++W3QJUxX7FbgP1uPUfkGWy1FKvqB6zBHifKU/7t2CqHbohKdg
         zXAy5RBEkdJLc6j8YD99WtrW66igC9golpTdznYdsZnsASMlNInNAUfO78zsrAEhqjWP
         HBK6tcFstoVJG2fUKLNiEgg6Lhcy49oYh212sjJj8Rn2q0fSYNxz0mzralFi1YyHu+Qy
         9hEA==
MIME-Version: 1.0
X-Received: by 10.60.246.139 with SMTP id xw11mr441111oec.36.1389945624973;
 Fri, 17 Jan 2014 00:00:24 -0800 (PST)
Received: by 10.76.131.101 with HTTP; Fri, 17 Jan 2014 00:00:24 -0800 (PST)
In-Reply-To: <52D86648.5010600@sugarcrm.com>
References: <CAPhkiZzW8g6PORyjrHFRTcUTLre+wM-sckZrNqRknkdgZrpr-w@mail.gmail.com>
	<52D83F13.3000702@ajf.me>
	<CAPhkiZxEU5xtJ6EYrrRi8-kK3jgi7HkuzSMxL0n4MR83Gky=5g@mail.gmail.com>
	<CAESVnVq3E87F2sWKwO69jaf7e0u6E=O6Y5TkMzC6WVQXpv2U8Q@mail.gmail.com>
	<52D86648.5010600@sugarcrm.com>
Date: Fri, 17 Jan 2014 09:00:24 +0100
Message-ID: <CAL-dKuM62-9Tv9y0TKBe-=eb3OSYmY=-QEGGzqHP_RH9s8B12A@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary=001a113696c03bd64804f025ef3b
Subject: Re: [PHP-DEV] Introducing "Array Of" RFC
From: iam.asm89@gmail.com (Alexander M)

--001a113696c03bd64804f025ef3b
Content-Type: text/plain; charset=ISO-8859-1

What I find interesting is that the title of the RFC is "Array Of",
proposing a type hint for an "array of Foo". In my opinion the proposed
syntax however reads more as "Foos in an array"?

Foo[] => Foo in/as an array
array<Foo> => array of Foo

I personally like the idea of array<Foo> because it seems to leave more
room for improvements and additions over time (nesting array<array<Foo>>,
k/v typehints array<Foo, Bar>).

Best,
Alexander

--001a113696c03bd64804f025ef3b--