Re: Allowing NULL for some internal functions
| From: | Craig Francis | Date: | Sun, 27 Feb 2022 20:07:32 +0000 |
| Subject: | Re: Allowing NULL for some internal functions | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-117156@lists.php.net to get a copy of this message | ||
On Sat, 1 Jan 2022 at 23:17, Craig Francis <craig@craigfrancis.co.uk> wrote:
> Draft RFC:
> https://wiki.php.net/rfc/allow_null
>
To get a better idea on how I should progress this RFC, I've created a
simple quiz (well, modified an old script).
This is to decide if my RFC should either - continue to allow NULL to be
coerced when not using strict_types=1; or update some ~335 parameters to
explicitly allow NULL; or do we just ignore backwards compatibility and let
the current deprecation lead to a Fatal Error for everyone?
https://quiz.craigfrancis.co.uk/
As an aside, Juliette (@jrfnl) has confirmed that getting PHPCompatibility
to solve this problem will be "pretty darn hard to do" because it's "not
reliably sniffable" [1].
Craig
[1] https://twitter.com/jrf_nl/status/1497937320766496772