Hi internals

> > https://wiki.php.net/rfc/nullsafe_operator
>
> Unfortunately, we have found some new edge cases that are currently
> not handled.

So, we've decided to completely disallow the nullsafe operator in
write context. This means you can no longer use it on the left hand
side of an assignment. This change was made mostly due to technical
issues but some of the semantics were also not completely clear (e.g.
do we always execute the right hand side? which order? etc).

You can find a diff of the changes here:
https://github.com/iluuu1994/nullsafe-operator-rfc/compare/5df9d041d2d202e5fab02b5881f2c4dc1fd9bcce...v1

I realize that it's very much last-minute but I will be opening the
vote tomorrow unless there are any objections. This way we have a few
days to merge before the feature freeze if the RFC is accepted.

Ilija

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php

Reply via email to