Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117812
Message-ID: <c7865fb1-dbb5-0067-6850-5bf4548b507f@alec.pl>
Date: Sat, 28 May 2022 08:25:00 +0200
MIME-Version: 1.0
Content-Language: en-US
To: internals@lists.php.net
References: <CAFv4g+Ej4JbM9SzQ0iU-d8C4T+2XNo=8jnJ1uwfQ=skZZXx9Tg@mail.gmail.com>
 <2B63A776-11B9-49BF-AE0A-FCF7F4E738F2@craigfrancis.co.uk>
In-Reply-To: <2B63A776-11B9-49BF-AE0A-FCF7F4E738F2@craigfrancis.co.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: NULL Coercion Consistency
From: alec@alec.pl (Aleksander Machniak)

On 28.05.2022 04:36, Craig Francis wrote:
> On 8 Apr 2022, at 18:34, Craig Francis <craig@craigfrancis.co.uk> wrote:
>> I've written a new draft RFC to address the NULL coercion problems:
>> https://wiki.php.net/rfc/null_coercion_consistency
> 
> I give up.

Don't give up. You have my Yes vote.

Imo, the RFC:
- fixes real upgrade problem (very important),
- improves consistency in a better way than the solution introduced in 8.1.
- does not change strict_types behavior

Some people don't care with what arguments their functions are called 
with. As long as the value can be coerced to the expected type the 
function will do what it is supposed to do. Other people have 
strict_types. All people don't want to be forced to modify a working code.

So, this is another "battle" between strict and non-strict camps. I'd 
like to see which is the majority these days. I hope that even some 
strict-code proponents can see this makes sense.

-- 
Aleksander Machniak
Kolab Groupware Developer        [https://kolab.org]
Roundcube Webmail Developer  [https://roundcube.net]
----------------------------------------------------
PGP: 19359DC1 # Blog: https://kolabian.wordpress.com