Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117316
MIME-Version: 1.0
References: <CAFPFaMJ9mONGwH1McEw-gfmH8KGAG6y9=Fgz-GHcNV0dvVWmJw@mail.gmail.com>
In-Reply-To: <CAFPFaMJ9mONGwH1McEw-gfmH8KGAG6y9=Fgz-GHcNV0dvVWmJw@mail.gmail.com>
Date: Sat, 12 Mar 2022 15:18:24 -0300
Message-ID: <CAEsg9X1d-PqegYoR3bD4KbScmJjNuZ28jDfsXicic7za9aScNg@mail.gmail.com>
To: "G. P. B." <george.banyard@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000bf22d305da09795a"
Subject: Re: [PHP-DEV] [RFC] [VOTE] Allow null and false as stand-alone types
From: david.proweb@gmail.com (David Rodrigues)

--000000000000bf22d305da09795a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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.


Atenciosamente,
David Rodrigues


Em s=C3=A1b., 12 de mar. de 2022 =C3=A0s 14:32, G. P. B. <george.banyard@gm=
ail.com>
escreveu:

> I've started voting for the Allow null and false as stand-alone types RFC=
:
> https://wiki.php.net/rfc/null-false-standalone-types
>
> Voting will last for 2 weeks until 26th of March.
>
> Best regards,
>
> George P. Banyard
>

--000000000000bf22d305da09795a--