Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108399
MIME-Version: 1.0
References: <861afae0-4568-745f-6615-a252067cc506@aimeos.com>
 <f0c665ca-02c3-da16-bb78-30d68f6e505e@aimeos.com> <5f5a4ab3-e609-4324-b056-53f782f1a63b@www.fastmail.com>
 <d9ed2493-0273-a4b2-7ec3-9aee06457325@aimeos.com>
In-Reply-To: <d9ed2493-0273-a4b2-7ec3-9aee06457325@aimeos.com>
Date: Tue, 4 Feb 2020 18:17:40 +0000
Message-ID: <CALKiJKr-ZHb4sqWERe=GAWJLkp_gcqGuaZoc06nz3=VPXrxY=A@mail.gmail.com>
To: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000cf3fd0059dc40ea8"
Subject: Re: [PHP-DEV] Re: [RFC] "arrayable" pseudo type hint
From: rowan.collins@gmail.com (Rowan Tommins)

--000000000000cf3fd0059dc40ea8
Content-Type: text/plain; charset="UTF-8"

On Tue, 4 Feb 2020 at 18:06, Aimeos | Norbert Sendetzky <norbert@aimeos.com>
wrote:

> Am 04.02.20 um 18:18 schrieb Larry Garfield:
> > The more I think on it, the less I like `arrayable`.  PHP arrays are
> > a terrible data structure from a type system point of view, with too
> > much functionality crammed into one variable type.
>
> The array internals are outside the scope of this proposal and are not
> affected in any way by this proposal.
>


I think Larry's point was that the flexibility of PHP's array type makes it
really hard to pin down whether a given object is "array-like" or not, and
which attributes a particular function actually cares about.

A general "intersection type" system might be more useful, because then you
could require the parts you specifically needed, such as
"traversable&ArrayAccess" or "traversable&countable".

Regards,
-- 
Rowan Tommins
[IMSoP]

--000000000000cf3fd0059dc40ea8--