> On 2 Dec 2022, at 01:21, Larry Garfield wrote:
>
> On Wed, Nov 30, 2022, at 7:38 PM, Stephen Reay wrote:
>
So please, can you explain to me why consistency with an implementation
detail of readonly properties is more important than consistency with
declared developer intenti
Hi
On 12/1/22 19:22, Ilija Tovilo wrote:
https://wiki.php.net/rfc/list_assoc_unique
This RFC proposes adding two new functions, List\unique() and
Assoc\unique() as alternatives using strict equality (===) semantics,
the former discarding and the latter preserving keys.
I believe this would b
Hi
On 11/29/22 21:29, Larry Garfield wrote:
Thank you everyone for the feedback. Based on this thread, we've made two
changes to the RFC:
1. We've moved readonly back to forbidden with a-viz for now. I've added a
section to Future Scope where we really should sort this out in the future, bu
Hi everyone
After the discussion on adding a new ARRAY_UNIQUE_IDENTICAL flag has
revealed that most would prefer a new function I've decided to create
an RFC for this.
https://wiki.php.net/rfc/list_assoc_unique
This RFC proposes adding two new functions, List\unique() and
Assoc\unique() as alter
On Wed, Nov 30, 2022, at 7:38 PM, Stephen Reay wrote:
>>> So please, can you explain to me why consistency with an implementation
>>> detail of readonly properties is more important than consistency with
>>> declared developer intention for regular properties via the magic
>>> setter method?
>>
