Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101668
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.21.1801251620210.24989@singlemalt.home.derickrethans.nl>
References: <CAEUnE0cRR6jtU2GoeiP4SDLJejF4+6zY=fT1FiTKPe6aKwoFqg@mail.gmail.com>
 <alpine.DEB.2.21.1801251441310.24989@singlemalt.home.derickrethans.nl>
 <CAObuZdsZf7t+VVjouk5qmsXmpBbQE5_BvfK4eTrS-pteFXubhA@mail.gmail.com> <alpine.DEB.2.21.1801251620210.24989@singlemalt.home.derickrethans.nl>
Date: Thu, 25 Jan 2018 09:31:00 -0700
Message-ID: <CAObuZdvWWc6K9TKtC0UyTqGqUZhvajb969iLRX4=EHK0Oo7Zsw@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: Michael Morris <tendoaki@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="001a1137b5c42c826705639c4e51"
Subject: Re: [PHP-DEV][RFC][DISCUSSION] Collection Inspection
From: derokorian@gmail.com (Ryan Pallas)

--001a1137b5c42c826705639c4e51
Content-Type: text/plain; charset="UTF-8"

On Thu, Jan 25, 2018 at 9:21 AM, Derick Rethans <derick@php.net> wrote:

> On Thu, 25 Jan 2018, Ryan Pallas wrote:
>
> > On Thu, Jan 25, 2018 at 7:52 AM, Derick Rethans <derick@php.net> wrote:
> >
> > > On Wed, 24 Jan 2018, Michael Morris wrote:
> > >
> > > > Ok, here's another idea I've been mulling over. This I know is
> possible
> > > > because I've done it using user land code, specifically Drupal 8's
> > > > Assertion\Inspector class.
> > > >
> > > > https://api.drupal.org/api/drupal/core%21lib%21Drupal%
> > > 21Component%21Assertion%21Inspector.php/class/Inspector/8.5.x
> > > >
> > > > These methods provide a means to inspect collections - arrays
> usually but
> > > > also Traversables. They fill a hole in the PHP library - the ability
> to
> > > > check collection integrity.
> > >
> > > IMO, it makes a lot more sense to check integrity when creating the
> > > "array" structure. Instead, I would suggest to add a native Collection
> > > type, that takes a "type" as argument. They aren't quite full generics,
> > > but it does 1. fix something; 2. isn't really complicated.
> > >
> > > What I am suggesting is to add a new syntax "Collection<$type>",
> > > mimicking a class, but having a type as "argument":
> > >
> > >
> > Just like to point out if it's considered a class, or takes the same
> space
> > there is likely collisions. While most collection classes on github look
> to
> > be in a namespace, there are lots that aren't. Of course github only
> gives
> > us a view of open source projects that happen to be on github.
>
> PHP owns the top-level namespace. It has always done that. It's even
> documented: http://docs.php.net/manual/en/userlandnaming.rules.php


And yet, it's a point of contention that every proposal adding to the root
namespace has faced.


>
>
> cheers,
> Derick
>
> --
> https://derickrethans.nl | https://xdebug.org | https://dram.io
> Like Xdebug? Consider a donation: https://xdebug.org/donate.php,
> or become my Patron: https://www.patreon.com/derickr
> twitter: @derickr and @xdebug
>

--001a1137b5c42c826705639c4e51--