Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111836
MIME-Version: 1.0
References: <DM6PR07MB6618683DF0ABBA43C4FC7CB8F9510@DM6PR07MB6618.namprd07.prod.outlook.com>
 <CAF+90c-OC8MC9U9GUkctizWVDPnVjuA6nibWgnV8c1Whyw+wLw@mail.gmail.com>
 <CANS-=pdjm2CraKmX-p-6OP1gpdnnTzSx6m2BggddDk5O4Hh89w@mail.gmail.com>
 <DM6PR07MB6618241A1FEA3234C4E38A7EF92E0@DM6PR07MB6618.namprd07.prod.outlook.com>
 <CAF+90c_V6AYLR3igJWqV-BLXmHeL+ZTuCzXCxHP1-sQ4f+me+g@mail.gmail.com>
In-Reply-To: <CAF+90c_V6AYLR3igJWqV-BLXmHeL+ZTuCzXCxHP1-sQ4f+me+g@mail.gmail.com>
Date: Thu, 3 Sep 2020 23:08:41 +0300
Message-ID: <CAJW__o3mRJPbo9-iSj=LhBXDNSGAMMO-D8MgjtQfpkur+is=TQ@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: tyson andre <tysonandre775@hotmail.com>, Lynn <kjarli@gmail.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] Global functions any() and all() on iterables
From: kalle@php.net (Kalle Sommer Nielsen)

Den tor. 3. sep. 2020 kl. 15.18 skrev Nikita Popov <nikita.ppv@gmail.com>:
> The main thing I'm concerned about is that once we start extending this
> area (I assume that any & all are not going to be the last additions in
> this space) we will quickly run into function names that are either too
> generic or outright collide. For example, what if we want to add an
> iterator-based version of range()? Do we *really* want to be forced to pull
> a Python and call it xrange()? That's about as good as real_range()...

I agree with this point, and we already have some `iterator_*`
functions in ext/spl. Such as `iterator_to_array()`,
`iterator_count()` and `iterator_apply()`, so that prefix is somewhat
available to use for consistency.


-- 
regards,

Kalle Sommer Nielsen
kalle@php.net