Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128078
Date: Wed, 16 Jul 2025 13:14:14 +0100 (BST)
To: "Gina P. Banyard" <internals@gpb.moe>
cc: PHP internals <internals@lists.php.net>
Subject: Re: [PHP-DEV][RFC] Deprecate type juggling to and from bool type
 within the function type juggling context
In-Reply-To: <bvjVobCbLKyWiVoKMNH_rtLH0_qZ5Jf2zi9FPqqpaIXNwNXi-niyI4yPc5SgLn0clNXeRvOLo0KWS2ma2o3CTMmczL5anK8G_56xi1wFegg=@gpb.moe>
Message-ID: <70524ffe-82ab-3b31-8913-bb8124a8cb92@php.net>
References: <3Yl0UGauXmKqk7s7Hqbv6iaXru-hZHf8Wj6VjwwihgRSaqZo5EZ2ndsOle-ae41C-lvnirynWt6PpuD7UJPL0zPCw18QHFE81Eb--fiiEbc=@gpb.moe> <bvjVobCbLKyWiVoKMNH_rtLH0_qZ5Jf2zi9FPqqpaIXNwNXi-niyI4yPc5SgLn0clNXeRvOLo0KWS2ma2o3CTMmczL5anK8G_56xi1wFegg=@gpb.moe>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="8323329-932340089-1752667914=:52945"
From: derick@php.net (Derick Rethans)

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323329-932340089-1752667914=:52945
Content-Type: text/plain; CHARSET=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Thu, 26 Jun 2025, Gina P. Banyard wrote:

> On Monday, 2 June 2025 at 17:11, Gina P. Banyard <internals@gpb.moe> wrot=
e:
>=20
> > This is the first RFC out of a set of type system related RFCs I=20
> > want to propose for PHP 8.5. It also used the recently enabled=20
> > Markdown support on the wiki, so there might be a few oddities.
> >=20
> > The RFC proposes to deprecate implicit type coercions to and from=20
> > the bool type for other scalar types. This a "weak" mode change=20
> > only, as when strict_types are enabled none of these coercions can=20
> > happen.
> >=20
> > Let me know what you think about it.
> >=20
> > RFC: https://wiki.php.net/rfc/deprecate-function-bool-type-juggling
>=20
> I have updated the RFC to version 0.2 that expands on it and addresses=20
> some of the counterarguments which were said during the discussion.=20
> RFC: https://wiki.php.net/rfc/deprecate-function-bool-type-juggling
>=20
> If there is no-follow up feedback, I will open the vote for it=20
> sometime next week.

I am sorry to say, but this RFC seems to be mostly to have a 'purity'=20
argument behind it.

The RFC also does not seems to include an analysis=20
of the impact.

I can almost guarantee you that this is going to 'break'=20
(by a deprecation warning?) a lot of code. Even the changes made for=20
symfony seem non-trivial, and easy to get wrong=20
(https://github.com/symfony/symfony/pull/60890/files).

But we don't know, as there is no data on this =E2=80=94 that's why I feel =
that=20
this is not a mature enough RFC.

cheers,
Derick
--8323329-932340089-1752667914=:52945--