Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129084
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>
 <CAMU7irKUDV=mtQW-XAoi-WZhNDoE-K4Sv88=2HWUWUcKsJTq4A@mail.gmail.com> <9BE876E9-93BE-44C5-9C12-8E2C6FF0766F@rwec.co.uk>
In-Reply-To: <9BE876E9-93BE-44C5-9C12-8E2C6FF0766F@rwec.co.uk>
Date: Wed, 5 Nov 2025 09:38:44 +0100
Message-ID: <CAMU7irLKxjiwgssh5BET1Gy1KSwDrN8ipyu5G4EjCHCL_5WLuw@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Nullable and non-nullable cast operators
To: "Rowan Tommins [IMSoP]" <imsop.php@rwec.co.uk>
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 Rowan,

> What you are proposing is a new syntax that changes step 5 to "else, thro=
w a TypeError". That might be a useful feature in some cases, but it's noth=
ing to do with the title of the RFC.

What we propose is to align these new operators to already existing
rules applied to function arguments. This is, indeed, stricter than
current cast operators. But I wouldn't say it has *nothing to do* with
the title of the RFC.
Maybe it's not perfectly accurate. If the naming is a problem and
should be changed, I'd be happy to hear suggestions and update
accordingly with a better name.

=E2=80=94 Alexandre Daubois