Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:117160 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 85428 invoked from network); 28 Feb 2022 10:07:14 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 28 Feb 2022 10:07:14 -0000 To: internals@lists.php.net Date: Mon, 28 Feb 2022 11:28:09 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1 Content-Language: en-GB References: <983552d8-11f1-b5bc-fb82-148347982fda@gmx.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 87.81.129.66 Subject: Re: [PHP-DEV] Allowing NULL for some internal functions From: marandall@php.net (Mark Randall) Message-ID: On 28/02/2022 01:46, Craig Francis wrote: > Personally I think `strict_types=1` is fine for my code, but I would never > want to force that style on everyone, because doing so would be fairly > hostile for a language that's popular and well known for being easy to > use/learn. Magically coercing things and hiding things under the hood is useful for the first 10 minutes of learning. After that it just becomes a hindrance difficult because you have to know all of the secret rules about type juggling.