Re: Nullable types and strict type-hinting with default null value

From: Date: Sat, 25 Feb 2017 15:12:35 +0000
Subject: Re: Nullable types and strict type-hinting with default null value
References: 1 2 3 4 5  Groups: php.internals 
Request: Send a blank email to internals+get-98351@lists.php.net to get a copy of this message
Hi, Rowan Collins wrote:
On 23 February 2017 09:15:27 GMT+00:00, "Michał" <aaatoja@o2.pl> wrote:
And what about situation when someone is forcing declare(strict_types=1)? I think, it's really a good place to force proper types. Including nulls.
strict_types controls the behaviour of *calling* functions, but the check here would have to be when *defining* the function: it would give an error that the function definition is invalid, like if you say function foo(int $bar='hello') Unless you had some other behaviour in mind?
In addition to this, if we wanted to prohibit implicit nullability in parameter definitions, we should have done it when we introduced declare(strict_types=1); in the first place, and that ship has sailed. -- Andrea Faulds https://ajf.me/

« previous php.internals (#98351) next »