Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:98345 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 20904 invoked from network); 23 Feb 2017 09:15:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Feb 2017 09:15:33 -0000 X-Host-Fingerprint: 89.231.48.169 host-89-231-48-169.dynamic.mm.pl Received: from [89.231.48.169] ([89.231.48.169:1780] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C8/5B-11648-338AEA85 for ; Thu, 23 Feb 2017 04:15:32 -0500 Message-ID: To: internals@lists.php.net References: Date: Thu, 23 Feb 2017 10:15:27 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 89.231.48.169 Subject: Re: [PHP-DEV] Nullable types and strict type-hinting with default null value From: aaatoja@o2.pl (=?UTF-8?Q?Micha=c5=82?=) > Indeed, it's far too early to think about forcing people to change all their code to the ? notation. I'm also not convinced of the value even once that's established; it's not like "Foo $foo = null" can ever mean *something different* from "?Foo $foo = null", it would just be an error. > > Maybe in 10 years' time we'll have another bonfire of unused features, and this might be one, but it's not something we can plan for right now. > 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.