Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117503
MIME-Version: 1.0
References: <CAFv4g+Ej4JbM9SzQ0iU-d8C4T+2XNo=8jnJ1uwfQ=skZZXx9Tg@mail.gmail.com>
 <B38CB916-9804-40D3-88E9-500C2908432C@dafert.at>
In-Reply-To: <B38CB916-9804-40D3-88E9-500C2908432C@dafert.at>
Date: Fri, 8 Apr 2022 19:07:37 +0100
Message-ID: <CAFv4g+F0LPhzBaHntiAidjHDyPLzFj=X=rnDqfkKGUenaVKWoA@mail.gmail.com>
To: Mel Dafert <mel@dafert.at>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000e7270d05dc2878c7"
Subject: Re: [PHP-DEV] NULL Coercion Consistency
From: craig@craigfrancis.co.uk (Craig Francis)

--000000000000e7270d05dc2878c7
Content-Type: text/plain; charset="UTF-8"

On Fri, 8 Apr 2022 at 18:54, Mel Dafert <mel@dafert.at> wrote:

> In particular, does this propose changing user-defined functions under
> strict_types=0 to accept null for scalar types?
>
> Eg., this will be allowed (under strict_types=0):
> ```
> function x(string $y, int $z) {
>   ...
> }
> x(null, null); //no error, no warning
> ```
>


tbh my focus has been on the problems that have come up with internal
functions.

With user defined functions, I think it's up for debate (still a draft),
but I think those NULL's should be coerced to the specified type (as
documented), where I don't think PHP should be doing type checking under
strict_types=0.

Craig

--000000000000e7270d05dc2878c7--