Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123164
Message-ID: <23f2275a-7a26-4f8a-b5c1-d92ed0298d1a@bastelstu.be>
Date: Fri, 19 Apr 2024 23:29:21 +0200
Precedence: bulk
MIME-Version: 1.0
Subject: Re: [PHP-DEV] RFC [Discussion]: array_find
To: =?UTF-8?Q?Joshua_R=C3=BCsweg?= <josh@wcflabs.de>,
 Larry Garfield <larry@garfieldtech.com>,
 PHP internals <internals@lists.php.net>
References: <24e4529d-0b75-44de-90ef-34de5dfb1c99@wcflabs.de>
 <278889be-82ab-4827-a9e7-801b5ba2d8f8@app.fastmail.com>
 <45b726f4-8085-43e2-b701-6b35bc249409@wcflabs.de>
 <d8a92e7a-539e-4753-bd27-5d59b17779ba@bastelstu.be>
Content-Language: en-US
In-Reply-To: <d8a92e7a-539e-4753-bd27-5d59b17779ba@bastelstu.be>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

On 4/9/24 21:49, Tim Düsterhus wrote:
> However I'm not sure if adding new array functions piecemeal is the
> right choice at this point. array_any and array_every are conceptually
> very similar to array_find and are missing as well. In fact
> array_any($cb, $array) = array_find($cb, $array, true) !== null and
> array_every($cb, $array) = !array_any($negatedCb, $array), but it would
> make sense to have them explicitly for clarity of the reader of the code.

Thinking about this: I believe that it would make sense to bundle 
array_any and array_every (or array_all, see below) within the same RFC 
due to the similarity. It can be a separate vote for those two, but 
having the option of getting all three would probably alleviate my 
concerns of adding new array functions piecemeal.

The implementation should be trivial, because it effectively just 
changes the return type. Nevertheless I'm happy to assist should any 
issues arise.

As for the naming:

JavaScript: every      + some
Haskell   : all        + any
Rust      : all        + any
C++       : all_of     + any_of + none_of
Java      : allMatch   + anyMatch (in java.util.stream.Stream)
Swift     : allSatisfy + contains(where: …)

It appears the commonly used choice is all + any.

Best regards
Tim Düsterhus