Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117317
MIME-Version: 1.0
References: <CAFPFaMJ9mONGwH1McEw-gfmH8KGAG6y9=Fgz-GHcNV0dvVWmJw@mail.gmail.com>
 <CAEsg9X1d-PqegYoR3bD4KbScmJjNuZ28jDfsXicic7za9aScNg@mail.gmail.com>
In-Reply-To: <CAEsg9X1d-PqegYoR3bD4KbScmJjNuZ28jDfsXicic7za9aScNg@mail.gmail.com>
Date: Sat, 12 Mar 2022 18:30:00 +0000
Message-ID: <CAFPFaM+TZgBeu8j+wjP3PCydWyqqPY7U-15YVzCrpGgSCnrJhA@mail.gmail.com>
To: David Rodrigues <david.proweb@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003e21ce05da09a3ec"
Subject: Re: [PHP-DEV] [RFC] [VOTE] Allow null and false as stand-alone types
From: george.banyard@gmail.com ("G. P. B.")

--0000000000003e21ce05da09a3ec
Content-Type: text/plain; charset="UTF-8"

On Sat, 12 Mar 2022 at 18:18, David Rodrigues <david.proweb@gmail.com>
wrote:

> Maybe I'm a little late to this discussion, but is there any reason why
> *false|null* is allowed but *true|null* is not?
>
> I can think of few cases where *true|null* could be interesting, but I've
> been through situations like this.
>

true is not a type in PHP compared to false, therefore it is not included.
I'm working on a proposal to add true as a type to PHP, but that's a
seperate RFC and discussion.

Best regards,

George P. Banyard

--0000000000003e21ce05da09a3ec--