Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112621
MIME-Version: 1.0
References: <DM6PR07MB661827026586104D5DEDAA64F9C20@DM6PR07MB6618.namprd07.prod.outlook.com>
 <CAAKU0ukPqFrEC2qUXOAL7T8wRcfonWiA8HQdckC7GuMYTOBC6g@mail.gmail.com>
In-Reply-To: <CAAKU0ukPqFrEC2qUXOAL7T8wRcfonWiA8HQdckC7GuMYTOBC6g@mail.gmail.com>
Date: Sat, 26 Dec 2020 17:59:58 +0100
Message-ID: <CANUQDCg_ixVeYyB52s0Gc0GNPDvPDuWa62yNxYo+-Jsa+geuCg@mail.gmail.com>
To: Levi Morrison <levi.morrison@datadoghq.com>
Cc: tyson andre <tysonandre775@hotmail.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000cb298305b760ff88"
Subject: Re: [PHP-DEV] Straw poll: Naming for `*any()` and `*all()` on iterables
From: me@kelunik.com (Niklas Keller)

--000000000000cb298305b760ff88
Content-Type: text/plain; charset="UTF-8"

>
> I want to re-iterate my opinion on this discussion thread: anything
> with a prefix is a hard-no from me. Namespaces are literally designed
> for this, and I will not vote "yes" to `iter_all`, `iterable_all`,
> etc, no matter what the prefix is. Anything without a namespace is a
> no from me.
>
> I'm flexible on many other points, but not this one. It's 2020 (almost
> 2021); let's use namespaces for what they were designed for. This is a
> perfect opportunity; they work on more than just arrays so using the
> `array_` prefix for consistency doesn't apply.
>

Hey Levi,

while I agree that namespaces were designed for this, I think `all` and
`any` are too generic names, even in a namespace.

I think Java's naming with any_match / all_match could be a good fit.

If promises / futures make it into core in the future, there will be a need
for an `any` / `all` function combining promises / futures.

Maybe these should be named `array_*` and all array functions should be
adjusted to work with iterators?

Best,
Niklas

--000000000000cb298305b760ff88--