Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130361
Message-ID: <995ce501-9106-4485-92b0-7bca3002a565@varteg.nz>
Date: Mon, 16 Mar 2026 13:41:30 +1300
Precedence: list
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] Array arguments for str functions
To: internals@lists.php.net
References: <CABVsipj2zp8tmZpY0WVUFrLNDJCOdpfege7PCFEwzt-XgpBn4A@mail.gmail.com>
Content-Language: en-GB
In-Reply-To: <CABVsipj2zp8tmZpY0WVUFrLNDJCOdpfege7PCFEwzt-XgpBn4A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: Weedpacket@varteg.nz (Morgan)

On 2026-03-15 20:20, Barel wrote:
> Hi all,
> 
> I would like to create an RFC proposal suggesting modifying the | 
> str_contains, |str_starts_with and str_ends_with functions so that they 
> can accept an array argument for the |$needle| parameter (apart from 
> accepting a string as they do now). If an array is passed and the | 
> $haystack| string contains, starts with or ends with any of the strings 
> in the array then the functions will return true, otherwise returns false.
> 
> I looked at the RFCs where these functions were added and at the related 
> internal discussions and could not find any discussion about this 
> possibility.
> Before creating the RFC I would like to hear the thoughts of the group, 
> many thanks in advance
> 
> Cheers
> 
> Carlos

The functions were added after it was pointed out that userland 
implementations tended to result in the information being derived 
internally and then thrown away, requiring the user to reconstruct it; 
it made sense to yield that internal information directly.

For this extension, I'm not sure what the advantages are over simple 
function composition (array_any was introduced for exactly this sort of 
job and is applicable to any function). Or disadvantages (e.g. more 
complex function signature).