On Mon, 21 Feb 2022 at 09:04, Christoph M. Becker <cmbecke...@gmx.de> wrote:
> That "inconsistency" had been introduced with PHP 7.0.0, i.e. right when > scalar type declarations have been introduced. Passing a null to a > non-nullable parameter of a *userland* function throws a TypeError > Thanks Christoph, that's a good way of looking at it. Considering NULL has been passed to these internal function parameters for years, for a variety of reasons, and PHP has coerced it into an empty string, integer 0, float 0, or boolean false... I'm wondering if my RFC should focus on matching that expectation, so anyone not using `strict_types=1` does not need to make loads of hard-to-find/unnecessary edits; that way NULL would be treated the same as the other variable types (I appreciate arrays and objects don't get coerced, but I don't think anyone expects them to). Craig
