Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105202
MIME-Version: 1.0
References: <CAC5V6gh79y-i1cQ-XhDBiZTq5BNLDbpcHxNX22mXtYKYrCC94g@mail.gmail.com>
In-Reply-To: <CAC5V6gh79y-i1cQ-XhDBiZTq5BNLDbpcHxNX22mXtYKYrCC94g@mail.gmail.com>
Date: Wed, 10 Apr 2019 12:52:22 +0200
Message-ID: <CAF+90c90dRCU=iUCUhV95yyUbkKGOnM-p=UkMOoQXiCDY0kutg@mail.gmail.com>
To: Guilliam Xavier <guilliam.xavier@gmail.com>
Cc: PHP internals <internals@lists.php.net>, David Rodrigues <david.proweb@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000003c4beb05862ade6e"
Subject: Re: [PHP-DEV] [RFC] Nullable Casting
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000003c4beb05862ade6e
Content-Type: text/plain; charset="UTF-8"

On Sat, Apr 6, 2019 at 9:53 AM Guilliam Xavier <guilliam.xavier@gmail.com>
wrote:

> Hello internals,
>
> David and I would like to open the discussion on our joint RFC:
>
> https://wiki.php.net/rfc/nullable-casting
>
> Mainly, it would enable to use e.g. `(?int)$x` besides `(int)$x`.
>
> We are looking forward to your feedback and, if possible, help to fill
> in the "RFC Impact" subsections (hopefully "None" to all) as well as a
> review of the proposed implementation:
>
> https://github.com/php/php-src/pull/3764


I'm a bit concerned that there are two possible semantics for what (?int)
does:

 1. What I would intuitively expect: A fallible integer cast. I.e. try to
cast to integer and if not possible return null. So (?int) "foobar" becomes
null rather than 0.
 2. What this RFC proposes: A normal integer cast that leaves null alone.

Both behaviors make sense to me generally ... and if there are two ways to
interpret a piece of syntax, I'd say the syntax is not explicit enough.

Nikita

--0000000000003c4beb05862ade6e--