Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129016
Precedence: list
MIME-Version: 1.0
References: <CAMU7irLdQg3UVT-SLmyCLWm4Qp81jAcU5uw3Jt=qBpaJCCWWpg@mail.gmail.com>
 <E98C3CE4-3959-4376-A37B-E94E142B3ED6@rwec.co.uk> <CAMU7irLBUAU2t4Den6M8kpPD6wHppM=HphRgjbaiz8j-ZO93OQ@mail.gmail.com>
 <f6d9f646-cc4c-48d6-9017-b7f4966dcab2@rwec.co.uk> <CAPbW5OOg2gYe9z9Gnb_BthRS3XT_Gu1EZD4L64m3GXyOfttnLg@mail.gmail.com>
In-Reply-To: <CAPbW5OOg2gYe9z9Gnb_BthRS3XT_Gu1EZD4L64m3GXyOfttnLg@mail.gmail.com>
Date: Fri, 31 Oct 2025 10:05:35 +0100
Message-ID: <CAMU7irKUDV=mtQW-XAoi-WZhNDoE-K4Sv88=2HWUWUcKsJTq4A@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Nullable and non-nullable cast operators
To: HwapX <hwapx.dev@gmail.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: alex.daubois+php@gmail.com (Alexandre Daubois)

Hi,

> Why not create a separate RFC to deprecate and remove(9.0) this and other=
s strange cast behaviors.
>
> Then after it finishes decide how to processed with this one?

We did some research with Nicolas about deprecating casting null
instead of proposing a new `(!type)` operator. The idea did not make
it, and we explained why in this new section:
https://wiki.php.net/rfc/nullable-not-nullable-cast-operator#alternative_co=
nsidereddeprecating_null_casting

As for other strange (or "fuzzy") cast behaviors, we agree the current
situation is not ideal. It is inconsistent with the rules of typed
function parameters. We added the "Future scope" section to the RFC in
this regard: https://wiki.php.net/rfc/nullable-not-nullable-cast-operator#f=
uture_scope.
This is something we will investigate in the near future.

This is fortunately not a blocker to this RFC, as this would address
an orthogonal problem. As you said, we have plenty of time before 8.6!

=E2=80=94 Alexandre Daubois