Re: Re: array_unique optional compare-callback proposal

From: Date: Wed, 20 Nov 2013 19:02:39 +0000
Subject: Re: Re: array_unique optional compare-callback proposal
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-70242@lists.php.net to get a copy of this message 
Hi!

>> $newArray = array_unique($a, SORT_USERDEFINED, function ($a, $b) {
>>      return $a->getWrappedObject()->getIdentity() -  
>> $b->getWrappedObject()->getIdentity();
>> });
>>
>>
>> Actually my problem was a little different but you get the idea... And I  
>> think there will be even more usecases for this.

What I notice here is that if we add SORT_USERDEFINED, we need to add it
to all other sorts, otherwise it would be inconsistent - why SORT_*
works for all sort functions but SORT_USERDEFINED works only for one of
them? And that opens a bit of a can of worms because for many array
functions this already exists as u* aliases - usort, array_udiff, etc.

-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227

Thread (4 messages)

« previous php.internals (#70242) next »