Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128963
Message-ID: <a8bdf747-3ba0-4331-b9fd-3b9709c12070@varteg.nz>
Date: Sun, 26 Oct 2025 00:05:00 +1300
Precedence: list
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] RFC proposal for adding SORT_STRICT flag to
 array_unique()
To: internals@lists.php.net
References: <CAE1541vPXkgZsxfAiWJyosnhDksGT=2tDJyoYOcJtG16jZh9nA@mail.gmail.com>
 <48b2d4f5-2baa-4dac-9f13-163ac68a4adf@app.fastmail.com>
Content-Language: en-GB
In-Reply-To: <48b2d4f5-2baa-4dac-9f13-163ac68a4adf@app.fastmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: Weedpacket@varteg.nz (Morgan)

On 2025-10-25 21:23, Rob Landers wrote:
> 
> Other than the bytes in memory and how they’re laid out, I fail to see 
> how 100 is different from 100. They’re conceptually identical, and 
> array_* functions generally behave by **value**, not by **identity**.
 >

In the case of objects, "value" and "identity" are the same thing; 
without a __toString() method that always produces different strings for 
different objects, array_unique() can't be used to deduplicate an array 
of objects - which I find myself wanting to do on a fairly regular basis.

```
$uniques = array_values(array_combine(array_map(spl_object_id(...), 
$source_array), $source_array));
```