Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109814
MIME-Version: 1.0
References: <CAKuGYLSHXG=QSjPT5TCgf2KV-D+cMt=s4++sw38wy3Hwt1BuqQ@mail.gmail.com>
 <4c1cd016-1e41-4ebc-afc4-d8d3cd1c319b@www.fastmail.com> <CAKuGYLR_GxMdyNniRW93U=tHu3xr+g0VkzzoRRoH-jQx=sVegQ@mail.gmail.com>
 <31441489-11c6-4d99-9c53-6ac0e877f268@www.fastmail.com> <CAKuGYLT8Ros+bQtuuLmNWYsGLjzNJVUeChEyHH0k3bR4fRPb9Q@mail.gmail.com>
 <73b33704-ded2-4cbc-93bd-17e8874177f2@www.fastmail.com> <CAKuGYLTBdGcQVJGpoN=jhv47PUA6DKwcqD8AUUvoht+j_6RKuQ@mail.gmail.com>
 <CAAKU0ukagJjjm2DjiOLfnB1dzVnew90BXeGscVLHdug64a3dMw@mail.gmail.com> <CAKuGYLTeXnRo78ked7c9GDU0dn1TDYxjA6sY-2K0=w4fsiA9fQ@mail.gmail.com>
In-Reply-To: <CAKuGYLTeXnRo78ked7c9GDU0dn1TDYxjA6sY-2K0=w4fsiA9fQ@mail.gmail.com>
Reply-To: Levi Morrison <levi.morrison@datadoghq.com>
Date: Thu, 23 Apr 2020 08:19:32 -0600
Message-ID: <CAAKU0ukoOr8ooj2KWyiO1Z0eur_RmVtR2EeNTLVDFjOC+3-z+Q@mail.gmail.com>
To: Matthew Brown <matthewmatthew@gmail.com>
Cc: Larry Garfield <larry@garfieldtech.com>, php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Any interest in a list type?
From: internals@lists.php.net ("Levi Morrison via internals")

On Thu, Apr 23, 2020 at 8:16 AM Matthew Brown <matthewmatthew@gmail.com> wr=
ote:
>>
>> IIRC, they switched from object semantics to value semantics (like PHP
>> arrays). Can someone more knowledgeable confirm?
>
>
> Yes, sorry =E2=80=93 Hack introduced the vec type (with value semantics) =
in 2016 after they'd experimented first with Vector (object semantics). Use=
 of Vector is now discouraged.
>
> Details here: https://github.com/facebook/hhvm/issues/6451
>
> FB/Hack appears to be in the multi-year process of moving all PHP arrays =
to one of [vec/dict/keyset]. That's likely not an option for PHP itself, bu=
t having the _option_ of a vec equivalent (in this proposal "list") would m=
ake sense, I think.

Yeah, I already figured that value semantics would be preferred for
this. From the engine perspective, we probably wouldn't want to
special case these 3 types and would probably want to figure out some
way for at least internal classes to have value semantics. Any
contrarian opinions there, especially from main php-src contributors
like Nikita and Dmitry?