Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117683
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: <80ad3c3d-47e3-66ef-0969-8b0894cb2c63@alec.pl>
Date: Sat, 7 May 2022 09:55:55 +0100
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <BE9A15B6-BAEF-48C5-BED7-BC2B398953E7@craigfrancis.co.uk>
References: <CAFv4g+Ej4JbM9SzQ0iU-d8C4T+2XNo=8jnJ1uwfQ=skZZXx9Tg@mail.gmail.com>
 <80ad3c3d-47e3-66ef-0969-8b0894cb2c63@alec.pl>
To: Aleksander Machniak <alec@alec.pl>
Subject: Re: [PHP-DEV] NULL Coercion Consistency
From: craig@craigfrancis.co.uk (Craig Francis)

On 7 May 2022, at 06:59, Aleksander Machniak <alec@alec.pl> wrote:
>=20
> On 08.04.2022 19:34, Craig Francis wrote:
>> Hi,
>> I've written a new draft RFC to address the NULL coercion problems:
>> https://wiki.php.net/rfc/null_coercion_consistency
>=20
> As a voter, I'm in favor of this RFC.
>=20
> I suggest to rename "Documentation" section title to "Scalars coercion =
inconsistency" or sth like that, as this section isn't really much about =
the documentation, rather the current state.


Good point Aleksander, I started with 5 quotes from the Documentation, =
but you're right, the examples have grown a bit since then, and the =
second part does show the Current State, so I've gone with that heading =
(hope that's ok).

Craig