On 15/03/2022 23:02, Patrick ALLAERT wrote:
I am not against the fact this warning becomes an error per se. I am just
not very fan of cherry-picking an individual kind of problem (read:
notice/warning/error/...) and changing it without a more global frame.
I think we should try to hit all of them, ideally in time for PHP 9.
That was the premise behind: https://externals.io/message/116918
It will likely take several RFCs until we've got it in the state we want
it, some of those are more contentious than others (such as undefined
array indexes).
I think undefined property access should throw too, and will likely have
supermajority support, but let's do it in a separate RFC.
What I don't think we want is the entire package being blocked because a
particular item (i.e. array keys) is contentious.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
