Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128952
Precedence: list
MIME-Version: 1.0
References: <CAMU7irLdQg3UVT-SLmyCLWm4Qp81jAcU5uw3Jt=qBpaJCCWWpg@mail.gmail.com>
 <CANS-=pdgZepQ=WseaYkbLz4ZFn4khUGWnc9vcFP1n0GLxSyc+A@mail.gmail.com>
In-Reply-To: <CANS-=pdgZepQ=WseaYkbLz4ZFn4khUGWnc9vcFP1n0GLxSyc+A@mail.gmail.com>
Date: Fri, 24 Oct 2025 14:43:50 +0200
Message-ID: <CAMU7ir+sfS-JQY=BueTyBvfHYmF-DhQA4Ns6FZbJDtynuQnK-w@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] Nullable and non-nullable cast operators
To: Lynn <kjarli@gmail.com>
Cc: PHP internals list <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 Lynn,

>  - In the RFC the "Behavior Comparison Table" the colors make it hard to =
read what's listed in the table, could this be adjusted?

Unfortunately this is the default style rendered by the PHP website.
But I can see if plain text could help readability. Let me check.

> // would be nice if it incorporated an "isset check" as it's effectively =
treated as a null value
> $quantity =3D ((?int) $_POST['quantity']) ?? 0;

I understand that it would probably help, but we prefer to keep this
proposition consistent with the current coercion rules of the core and
avoid adding more special rules to the numerous existing ones.

=E2=80=94 Alexandre Daubois