Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111766 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 48773 invoked from network); 1 Sep 2020 21:05:28 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 1 Sep 2020 21:05:28 -0000 To: internals@lists.php.net References: Date: Tue, 1 Sep 2020 21:10:10 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Posted-By: 87.81.129.66 Subject: Re: [PHP-DEV] [RFC] Global functions any() and all() on iterables From: marandall@php.net (Mark Randall) Message-ID: On 01/09/2020 16:05, Levi Morrison via internals wrote: > Anyway, the key point I'm making is that I think a larger RFC has a > better shot of passing if we want to namespace it. Try as we might 4 of us working together couldn't get namespaces accepted. I got the feeling that there seems to be an opposition to them on principle, rather than the merits or drawbacks of the RFCs. Various libraries do use statics for this: Iterators::all()