Re: [RFC] Global functions any() and all() on iterables

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