Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113111
MIME-Version: 1.0
References: <DM6PR07MB66189594D6D3B6D820E4A5FBF98F9@DM6PR07MB6618.namprd07.prod.outlook.com>
 <CAAKU0ukKrfr54w-3NHiJRUtRgkptgnw8vb7QXvHXQhNbbcFhMg@mail.gmail.com>
In-Reply-To: <CAAKU0ukKrfr54w-3NHiJRUtRgkptgnw8vb7QXvHXQhNbbcFhMg@mail.gmail.com>
Date: Mon, 8 Feb 2021 17:14:02 +0200
Message-ID: <CAJW__o21UFKN3YWd=45PLtqjSSwM_wGkLtK5ebxK6kqCqNP93g@mail.gmail.com>
To: Levi Morrison <levi.morrison@datadoghq.com>
Cc: tyson andre <tysonandre775@hotmail.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [VOTE] PHP\iterable\any() and all() on iterables
From: kalle@php.net (Kalle Sommer Nielsen)

Den man. 8. feb. 2021 kl. 17.08 skrev Levi Morrison via internals
<internals@lists.php.net>:
> - I do not like the chosen namespace. This is not as important as the
> previous point, but still factored into my decision as we are still
> very early in choosing namespaces for internals. I don't want to vote
> for something I think is a bad direction when we're this early on.

I'm in a similar boat as Levi, I like the functionality but the
choosen namespace is what caused my no vote. We had 2 RFCs last year
talking about the namespace question and it is yet to be answered -- I
don't think this RFC or any other should go into the core as it could
force the answer to the namespace question. Having them in \ would be
a +1 from me tho.

-- 
regards,

Kalle Sommer Nielsen
kalle@php.net