Hi

On 7/20/24 03:14, Larry Garfield wrote:
We've made one change since we last discussed it:  Specifically, Ilija realized 
that __set's behavior is already inconsistent, so supporting it for aviz 
properties with invisible set would make it even more inconsistent, not less.  
For that reason, we've changed the __set behavior such that a non-readonly aviz 
property will not trigger __set.  Further details are in the RFC, but in short, 
all of the use cases for that behavior now have better alternatives, such as 
property types, hooks, and aviz itself.  So there's really no point to falling 
back to __set in edge cases.

https://wiki.php.net/rfc/asymmetric-visibility-v2#interaction_with_set_and_unset

Baring any new developments, we plan to start the vote early next week.

I find it unfortunate that this RFC received a non-trivial change on a Saturday after the discussion has been idle for more than a month together with the announcement that the vote will begin shortly after the weekend. Folks should be given sufficient time to react to the newest developments. Personally I plan to give this RFC another read, because I already forgot the details after a month of not looking at it, but I'm not sure if I'll manage today.

For now:

Is there any implementation of this RFC? The RFC text only references the https://github.com/php/php-src/pull/9257 PR hasn't been updated since December 2022.

Best regards
Tim Düsterhus

Reply via email to