Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117502
Date: Fri, 08 Apr 2022 19:54:59 +0200
To: Craig Francis <craig@craigfrancis.co.uk>,
 PHP internals <internals@lists.php.net>
User-Agent: K-9 Mail for Android
In-Reply-To: <CAFv4g+Ej4JbM9SzQ0iU-d8C4T+2XNo=8jnJ1uwfQ=skZZXx9Tg@mail.gmail.com>
References: <CAFv4g+Ej4JbM9SzQ0iU-d8C4T+2XNo=8jnJ1uwfQ=skZZXx9Tg@mail.gmail.com>
Message-ID: <B38CB916-9804-40D3-88E9-500C2908432C@dafert.at>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] NULL Coercion Consistency
From: mel@dafert.at (Mel Dafert)

On 8 April 2022 19:34:52 CEST, Craig Francis <craig@craigfrancis=2Eco=2Euk>=
 wrote:
>Hi,
>
>I've written a new draft RFC to address the NULL coercion problems:
>
>https://wiki=2Ephp=2Enet/rfc/null_coercion_consistency
>
>This is due to the result of the Allow NULL quiz:
>
>https://quiz=2Ecraigfrancis=2Eco=2Euk/
>
>14 votes for Fatal Type Errors irrespective of `strict_types=3D1`;
>13 votes for NULL coercion when not using `strict_types=3D1`;
>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=2E
>
>Breaking changes should be justified - if they aren't, they only
>make upgrading difficult and frustrating (bad for security)=2E
>
>Craig

Hello,

While the RFC extensively documents the problem space, it's rather short o=
n what
exactly it proposes=2E

In particular, does this propose changing user-defined functions under
strict_types=3D0 to accept null for scalar types?

Eg=2E, this will be allowed (under strict_types=3D0):
```
function x(string $y, int $z) {
  =2E=2E=2E
}
x(null, null); //no error, no warning
```

Regards,
Mel