Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111767
To: Nikita Popov <nikita.ppv@gmail.com>,
 tyson andre <tysonandre775@hotmail.com>
Cc: PHP internals <internals@lists.php.net>
References: <DM6PR07MB6618683DF0ABBA43C4FC7CB8F9510@DM6PR07MB6618.namprd07.prod.outlook.com>
 <CAF+90c-OC8MC9U9GUkctizWVDPnVjuA6nibWgnV8c1Whyw+wLw@mail.gmail.com>
Message-ID: <4792c245-ceda-d953-f844-ba26e02dc548@gmail.com>
Date: Tue, 1 Sep 2020 22:41:06 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <CAF+90c-OC8MC9U9GUkctizWVDPnVjuA6nibWgnV8c1Whyw+wLw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Global functions any() and all() on iterables
From: dik.takken@gmail.com (Dik Takken)

On 01-09-2020 09:30, Nikita Popov wrote:
> To be in line with naming conventions, I would suggest calling these
> iter_any() and iter_all(), using iter_* as the prefix for our future
> additions to the "functions that work on arbitrary iterables" space.
> iterable_any() and iterable_all() would work as well, though are
> unnecessarily verbose.

It would make a lot of sense if we end up having a set of array_*
functions and a set of iter_* functions. It would be nice for the RFC to
mention this as a possible future result.

However I am equally tempted to reason otherwise: Since the new
functions are generalizations of functions which only work for arrays,
strip the array_ prefixes off the existing array functions to create a
set of generalized counterparts. It does yield nice short function
names. :)

Also, it would not surprise me if the generalized functions gradually
replace the good old array functions in the future. When that happens, I
would rather not have the iter_ prefixes.

Regards,
Dik Takken