Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108202
Message-ID: <2525C530-9FF8-4C34-9E92-26E8380B53DD@newclarity.net>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_4C650DA9-43F1-4CF9-81DA-421E610FBA2A"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Sun, 19 Jan 2020 21:30:07 -0500
In-Reply-To: <191B2F45-C9F2-49EB-A19B-9C3D8A705AD6@zort.net>
Cc: PHP internals <internals@lists.php.net>
To: John Bafford <jbafford@zort.net>
References: <CAKtGGAsh-38W1UjgDaoQFzhKNOqTy3QGV8fE1-6-PPob2zw6Vw@mail.gmail.com>
 <CAF+90c8yAqHeLRzeX0sYxnQ30JAtg=Ubp7sDyonCkS5V7goN5A@mail.gmail.com>
 <5DC86728-1BBF-4DCA-8A6B-9B0B190DB99D@newclarity.net>
 <191B2F45-C9F2-49EB-A19B-9C3D8A705AD6@zort.net>
Subject: Re: [PHP-DEV] Typed array properties V2
From: mike@newclarity.net (Mike Schinkel)

--Apple-Mail=_4C650DA9-43F1-4CF9-81DA-421E610FBA2A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> On Jan 19, 2020, at 8:42 PM, John Bafford <jbafford@zort.net> wrote:
> As a thought, perhaps the syntax '[Type]' for an array of Type. That =
way, you could write ?[int], or [?int], or even ?[?int] and there would =
be no ambiguity, and no need for parentheses since the array brackets =
would serve that purpose.

That syntax was what someone suggested on the prior discussion. I =
personally dislike it because I have used PHPDoc syntax of `type[]` for =
so long and would rather see us stick with that.

But if I'm honest about it, debate over syntax is probably just =
bikeshedding at this point. =20

The more important question IMO is, can we actually implement typed =
arrays to enough voter's satisfaction and w/o a significant performance =
penalty?

-Mike


--Apple-Mail=_4C650DA9-43F1-4CF9-81DA-421E610FBA2A--