Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112575
MIME-Version: 1.0
References: <DM6PR07MB661827026586104D5DEDAA64F9C20@DM6PR07MB6618.namprd07.prod.outlook.com>
In-Reply-To: <DM6PR07MB661827026586104D5DEDAA64F9C20@DM6PR07MB6618.namprd07.prod.outlook.com>
Date: Mon, 21 Dec 2020 11:39:39 -0600
Message-ID: <CAESVnVoDShD_R0qRizmz06Whr4smEPOvy8jCCBJshKGw1jZ9zQ@mail.gmail.com>
To: tyson andre <tysonandre775@hotmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000e8c39905b6fcf197"
Subject: Re: [PHP-DEV] Straw poll: Naming for `*any()` and `*all()` on iterables
From: pollita@php.net (Sara Golemon)

--000000000000e8c39905b6fcf197
Content-Type: text/plain; charset="UTF-8"

On Sat, Dec 19, 2020 at 2:24 PM tyson andre <tysonandre775@hotmail.com>
wrote:

> 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
>
>
This is probably going to be a terrible idea because it involves a little
magic but...

"iterable" is already a forbidden userspace class name since it's reserved
for the psuedo-type which is a union of `Traversable | array`.

What if we went ahead and defined an actual (abstract-final) `iterable`
class.  The parser rules which treat `iterable` as a special type still
apply, so we never try to match instances of class `iterable`, but what we
can do is define methods on it.

class Iterable {
    static public function any(iterable $iter, Callable $predicate): bool {
... }
    static public function all(iterable $iter, Callable $predicate): bool {
... }
}

Then the API is both 100% searchable (the man page for iterable can explain
that it's a pseudo-type AND that it has helper methods), and intuitive to
read/write.

if (iterable::any($iter, fn($elem) => $elem === 'foo')) {

}

--000000000000e8c39905b6fcf197--