Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128947
Precedence: list
MIME-Version: 1.0
References: <CAMU7irLdQg3UVT-SLmyCLWm4Qp81jAcU5uw3Jt=qBpaJCCWWpg@mail.gmail.com>
In-Reply-To: <CAMU7irLdQg3UVT-SLmyCLWm4Qp81jAcU5uw3Jt=qBpaJCCWWpg@mail.gmail.com>
Date: Fri, 24 Oct 2025 11:21:58 +0200
Message-ID: <CANS-=pdgZepQ=WseaYkbLz4ZFn4khUGWnc9vcFP1n0GLxSyc+A@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Nullable and non-nullable cast operators
To: Alexandre Daubois <alex.daubois+php@gmail.com>
Cc: PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000071c0450641e416e7"
From: kjarli@gmail.com (Lynn)

--00000000000071c0450641e416e7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 24, 2025 at 9:09=E2=80=AFAM Alexandre Daubois <
alex.daubois+php@gmail.com> wrote:

> Hi everyone,
>
> Nicolas Grekas and I would like to propose this new RFC to the
> discussion. This proposes to introduce two new cast operators to the
> language: `(?type)` and `(!type)`.
>
> Please find the details here:
> https://wiki.php.net/rfc/nullable-not-nullable-cast-operator
>
> Thanks!
>
> =E2=80=94 Alexandre Daubois
>

This looks useful to me
 - In the RFC the "Behavior Comparison Table" the colors make it hard to
read what's listed in the table, could this be adjusted?
 - We still end up having null coalescing operators (or isset) for arrays,
would something like this work?
```
// suggested through RFC
$quantity =3D ((?int) ($_POST['quantity'] ?? null)) ?? 0;

// the underlying logic would be
$quantity =3D $_POST['quantity'] ?? null;
if ($quantity !=3D=3D null && ! is_valid_int_value($quantity)) {
    throw new TypeError();
}
$quantity =3D (int) $quantity;

// would be nice if it incorporated an "isset check" as it's effectively
treated as a null value
$quantity =3D ((?int) $_POST['quantity']) ?? 0;
```

--00000000000071c0450641e416e7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Oct 24,=
 2025 at 9:09=E2=80=AFAM Alexandre Daubois &lt;<a href=3D"mailto:alex.daubo=
is%2Bphp@gmail.com">alex.daubois+php@gmail.com</a>&gt; wrote:<br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex">Hi everyone,<br>
<br>
Nicolas Grekas and I would like to propose this new RFC to the<br>
discussion. This proposes to introduce two new cast operators to the<br>
language: `(?type)` and `(!type)`.<br>
<br>
Please find the details here:<br>
<a href=3D"https://wiki.php.net/rfc/nullable-not-nullable-cast-operator" re=
l=3D"noreferrer" target=3D"_blank">https://wiki.php.net/rfc/nullable-not-nu=
llable-cast-operator</a><br>
<br>
Thanks!<br>
<br>
=E2=80=94 Alexandre Daubois<br></blockquote><div><br></div><div>This looks =
useful to me</div><div>=C2=A0- In the RFC the &quot;Behavior Comparison Tab=
le&quot; the colors make it hard to read what&#39;s listed in the table, co=
uld this be adjusted?</div><div>=C2=A0- We still end up having null coalesc=
ing operators (or isset) for arrays, would something like=C2=A0this work?</=
div><div>```<br>// suggested through RFC<br>$quantity =3D ((?int) ($_POST[&=
#39;quantity&#39;] ?? null)) ?? 0;</div><div><br>// the underlying logic wo=
uld be<br>$quantity =3D $_POST[&#39;quantity&#39;] ?? null;</div><div>if ($=
quantity !=3D=3D null &amp;&amp; ! is_valid_int_value($quantity)) {<br>=C2=
=A0 =C2=A0 throw new TypeError();</div><div>}<br>$quantity =3D (int) $quant=
ity;<br><br>// would be nice if it incorporated an &quot;isset check&quot; =
as it&#39;s effectively treated as a null value<br>$quantity =3D ((?int) $_=
POST[&#39;quantity&#39;]) ?? 0;</div><div>```</div></div></div>

--00000000000071c0450641e416e7--