Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112598
MIME-Version: 1.0
References: <DM6PR07MB661827026586104D5DEDAA64F9C20@DM6PR07MB6618.namprd07.prod.outlook.com>
In-Reply-To: <DM6PR07MB661827026586104D5DEDAA64F9C20@DM6PR07MB6618.namprd07.prod.outlook.com>
Reply-To: Levi Morrison <levi.morrison@datadoghq.com>
Date: Tue, 22 Dec 2020 10:08:25 -0700
Message-ID: <CAAKU0ukPqFrEC2qUXOAL7T8wRcfonWiA8HQdckC7GuMYTOBC6g@mail.gmail.com>
To: tyson andre <tysonandre775@hotmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Straw poll: Naming for `*any()` and `*all()` on iterables
From: internals@lists.php.net ("Levi Morrison via internals")

On Sat, Dec 19, 2020 at 1:24 PM tyson andre <tysonandre775@hotmail.com> wrote:
>
> Hi internals,
>
> I've created a straw poll for the naming pattern to use for `*any()` and `*all()` on iterables.
> https://wiki.php.net/rfc/any_all_on_iterable_straw_poll
>
> Background: The RFC https://wiki.php.net/rfc/any_all_on_iterable proposes adding only two functions,
> but more functionality acting on iterables (array|Traversable) may be added in the future,
> making it important to get feedback what people feel the best choice of naming pattern would be
> to avoid inconsistency or name changes later on.
> (Many alternatives were suggested in the initial RFC announcement - https://externals.io/message/111756)

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.