Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123100
Message-ID: <9d928e90-933c-483f-8bb7-24f960dd926f@bastelstu.be>
Date: Wed, 10 Apr 2024 19:21:46 +0200
Precedence: bulk
MIME-Version: 1.0
Subject: Re: [PHP-DEV] RFC [Discussion]: array_find
To: 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>
 <2dd7ef64-d1c5-4ed8-964f-b86dba110e0d@app.fastmail.com>
Content-Language: en-US
In-Reply-To: <2dd7ef64-d1c5-4ed8-964f-b86dba110e0d@app.fastmail.com>
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/10/24 00:12, Larry Garfield wrote:
>> I feel the same. Adding an enum for each binary parameter that is
>> semantically true and false feels quite unwieldy with how class / enums
>> / interfaces are currently organized in the namespace hierarchy.
> 
> Point of order: This parameter is *not* semantically true and false.  It is semantically either/or, and we kinda twist sideways to make it look like true/false if we squint.  That's actually pretty common in the current stdlib, though it's not a good approach.  Hence why I asked about an enum.  I wouldn't expect it to be single-function, though, but to be applicable for multiple functions.  (I did not go looking to see if such functions exist.)

Whoops, I accidentally a word in that paragraph, thank you.

It should have read "each binary parameter that is NOT semantically true 
and false".

Best regards
Tim Düsterhus