On Mon, May 19, 2025, at 5:48 AM, Volker Dusch wrote: > Hey everyone, > > Thank you for the participation so far, since the start of the > discussion, from feedback on and off list, I've added a couple of > examples: > > - > https://wiki.php.net/rfc/clone_with_v2#:~:text=dynamic%20property%20creation%20follows%20established%20PHP%20rules > - https://wiki.php.net/rfc/clone_with_v2#:~:text=Positional%20parameters > - We removed the behavior of __clone locking readonly properties when > the function updates them for forward compatibility concerns raised in > https://externals.io/message/127353#127390 > - Updated https://wiki.php.net/rfc/clone_with_v2#design_goals > mentioning there that consider touching __clone or adding parameters a > non-goal due to complexity and BC implications. > - Updated the property name of the varadic parameter from > $updatedProperties to $withProperties > > We're still looking for feedback on the ...variadic approach to the > Syntax: https://wiki.php.net/rfc/clone_with_v2#open_issues, as we only > got one reply so far on the topic. > > Also thanks to theodorejb for touching up phrasing, correcting spelling > mistakes and so on: https://wiki.php.net/rfc/clone_with_v2?do=revisions > > Kind Regards, > Volker
For positional parameters, I don't see any way that they'd work or do what someone expects. So why not just block them entirely instead of relying on dynamic properties to warn-but-sorta-work? --Larry Garfield
