Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109709
MIME-Version: 1.0
References: <CAKtGGAsh-38W1UjgDaoQFzhKNOqTy3QGV8fE1-6-PPob2zw6Vw@mail.gmail.com>
 <CAF+90c8yAqHeLRzeX0sYxnQ30JAtg=Ubp7sDyonCkS5V7goN5A@mail.gmail.com>
 <CAKuGYLQbRFNt6vBe=PS4jHz8JkREkK07YPDh+7a9OoSyJvxbEw@mail.gmail.com> <11e910d3-8dbd-55ad-984b-516eba52b68c@php.net>
In-Reply-To: <11e910d3-8dbd-55ad-984b-516eba52b68c@php.net>
Date: Sun, 19 Apr 2020 18:53:26 -0400
Message-ID: <CAKuGYLR8JCceCXN=Epchsov1WrE1Lyo_4HV-ZSGj4DCytO2_VQ@mail.gmail.com>
To: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000002ccea905a3aca798"
Subject: Re: [PHP-DEV] Typed array properties V2
From: matthewmatthew@gmail.com (Matthew Brown)

--0000000000002ccea905a3aca798
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Yes!

Though I don't necessarily think they need to be genericised (e.g.
list<int>) in the language itself =E2=80=93 just having those alternate
datatypes would, I think, be a boon to the language itself =E2=80=93 with l=
ist (a
subtype of array) more useful to me than dict.


On Sat, 18 Apr 2020 at 10:51, Sebastian Bergmann <sebastian@php.net> wrote:

> Am 21.01.2020 um 22:21 schrieb Matthew Brown:
> > What if we left the array type alone, and instead focussed on "list<Foo=
>"
> > type and "dict<string, Foo>", "dict<int, Bar>" types?
> >
> > That would allow a clear break from previous behaviour, and would allow
> you
> > to introduce other changes (e.g. removing string -> int coercion for
> > numeric string keys).
>
> Just to make sure I understand you correctly: are you proposing new data
> structures, names list and dict, in addition to array that can bring more
> specific / strict semantics?
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--0000000000002ccea905a3aca798--