Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117735
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
In-Reply-To: <CAGBsUrdLdJGMg-0BH311fKJ+41EWL2eNQaLMMpY2XevNFSvW4Q@mail.gmail.com>
Date: Mon, 16 May 2022 17:18:50 +0100
Cc: Andreas Leathley <a.leathley@gmx.net>,
 PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <1CBFFD57-D712-4821-8B15-4498D052CB89@craigfrancis.co.uk>
References: <eb2bef11-4027-8555-93e3-89c2cc4f5a18@gmx.net>
 <CAGBsUrdLdJGMg-0BH311fKJ+41EWL2eNQaLMMpY2XevNFSvW4Q@mail.gmail.com>
To: Kamil Tekiela <tekiela246@gmail.com>
Subject: Re: [PHP-DEV] [Discussion] Stricter implicit boolean coercions
From: craig@craigfrancis.co.uk (Craig Francis)

On 16 May 2022, at 16:19, Kamil Tekiela <tekiela246@gmail.com> wrote:
> On 16 May 2022, at 16:06, Andreas Leathley <a.leathley@gmx.net> wrote:
>> https://wiki.php.net/rfc/stricter_implicit_boolean_coercions
>=20
> Has any case study been done already about how it will affect existing =
codebases?


The last time this happened there were no checks:

https://wiki.php.net/rfc/deprecate_null_to_scalar_internal_arg

https://externals.io/message/112327

And unfortunately the result was not good for that one :-(

But, at least with this RFC, I can see how some coercions can be =
problematic, like the string "false" being cast to true.

With any of these changes, I just wonder what the costs/benefits are, =
and if there are any edge cases / oddities.

Craig