Den 2022-04-08 kl. 19:34, skrev Craig Francis:
Hi,
I've written a new draft RFC to address the NULL coercion problems:
https://wiki.php.net/rfc/null_coercion_consistency
This is due to the result of the Allow NULL quiz:
https://quiz.craigfrancis.co.uk/
14 votes for Fatal Type Errors irrespective of `strict_types=1`;
13 votes for NULL coercion when not using `strict_types=1`;
8 votes to update some parameters to allow NULL;
I appreciate some want to force strict type checking on everyone, but I
want to make sure we have this properly documented, with names, and
explanations.
Breaking changes should be justified - if they aren't, they only
make upgrading difficult and frustrating (bad for security).
Craig
Hi,
Have been busy for a while and haven't followed all the details around
this RFC, but now back on track.
One code pattern to upgrade your code to PHP 8.1 and 9.0 is to use the
null coalescing operator like rtrim($string ?? '',...).
If one then has a legacy codebase that works flawlessly I would say that
this path is the preferred one since it requires a minimum of work. To
dig into your code base and address why the parameter ends up like null
is probably more cumbersome. OTOH, one doesn't reap the benefits of the
"Deprecate passing null to non-nullable arguments of internal functions"
RFC since it requires to much work.
One could argue that the "Deprecating passing null" RFC is nice, but has
a flaw when applied for existing code. Applying the null coalescing code
pattern is an easy way to make your code 8.1 compatible, but not sure if
it adds value to the application itself.
Now if this RFC is the best way to improve things if one think this is
something of an issue with the original RFC worth addressing I don't
know. But at least worth having a discussion about! The purist within
me sighs a little when applying the code pattern above...
r//Björn L
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
