Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128067
Feedback-ID: ifab94697:Fastmail
Precedence: bulk
MIME-Version: 1.0
Date: Tue, 15 Jul 2025 21:39:18 +0200
To: internals@lists.php.net
Message-ID: <277533a4-d50a-41ec-b753-b118c1e4ab69@app.fastmail.com>
In-Reply-To: 
 <ClHWqZ8xQp5NMLvOxMZ80CqdIr0QVhrCzJmDZyw0h7Z4CtK3DG8fW3dKbf4fu-WJRxvqBY9S_W29um3mHEaGJ9ee1epItOizujB3CpbNKfA=@gpb.moe>
References: 
 <ClHWqZ8xQp5NMLvOxMZ80CqdIr0QVhrCzJmDZyw0h7Z4CtK3DG8fW3dKbf4fu-WJRxvqBY9S_W29um3mHEaGJ9ee1epItOizujB3CpbNKfA=@gpb.moe>
Subject: Re: [PHP-DEV] [RFC] Warnings for PHP 8.5
Content-Type: multipart/alternative;
 boundary=7ca914bfbb1148d2ac667dcb1f62afac
From: rob@bottled.codes ("Rob Landers")

--7ca914bfbb1148d2ac667dcb1f62afac
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Mon, Jul 14, 2025, at 18:20, Gina P. Banyard wrote:
> Hello internals,
>=20
> Similar to the mass deprecation RFC, I would like to propose the addit=
ion of a few warnings in certain situations:
> https://wiki.php.net/rfc/warnings-php-8-5
>=20
> I am expecting these 4 sub-proposals to be mostly uncontroversial,
> other than possibly, the "Using offsets on non-container values in iss=
et()/empty()" one.
>=20
> As this is intended to land in PHP 8.5 the discussion will last 2 week=
s and voting will commence on Monday the 28th of July 2025.
>=20
> Best regards,
>=20
> Gina P. Banyard
>=20

Hi Gina, I feel like destructuring `null` should not be the same warning=
 as other types since null auto-vivicates? to [] (an empty array). Inste=
ad, it should provide the same warning as https://3v4l.org/8QPiD.

=E2=80=94 Rob
--7ca914bfbb1148d2ac667dcb1f62afac
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title></head><body><div>On Mon, Jul =
14, 2025, at 18:20, Gina P. Banyard wrote:</div><blockquote type=3D"cite=
" id=3D"qt" style=3D""><div>Hello internals,</div><div><br></div><div>Si=
milar to the mass deprecation RFC, I would like to propose the addition =
of a few warnings in certain situations:</div><div><a href=3D"https://wi=
ki.php.net/rfc/warnings-php-8-5">https://wiki.php.net/rfc/warnings-php-8=
-5</a></div><div><br></div><div>I am expecting these 4 sub-proposals to =
be mostly uncontroversial,</div><div>other than possibly, the "Using off=
sets on non-container values in isset()/empty()" one.</div><div><br></di=
v><div>As this is intended to land in PHP 8.5 the discussion will last 2=
 weeks and voting will commence on Monday the 28th of July 2025.</div><d=
iv><br></div><div>Best regards,</div><div><br></div><div>Gina P. Banyard=
</div><div><br></div></blockquote><div><br></div><div>Hi Gina, I feel li=
ke destructuring `null` should not be the same warning as other types si=
nce null auto-vivicates? to [] (an empty array). Instead, it should prov=
ide the same warning as&nbsp;<a href=3D"https://3v4l.org/8QPiD">https://=
3v4l.org/8QPiD</a>.<br></div><div><br></div><div id=3D"sig121229152">=E2=
=80=94 Rob</div></body></html>
--7ca914bfbb1148d2ac667dcb1f62afac--