Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117122
MIME-Version: 1.0
References: <CAFPFaMJoV+9-gNi3gMB_Jyz=_3ZRWZCXSjVknX6h3Fqm6p7kmg@mail.gmail.com>
In-Reply-To: <CAFPFaMJoV+9-gNi3gMB_Jyz=_3ZRWZCXSjVknX6h3Fqm6p7kmg@mail.gmail.com>
Date: Wed, 23 Feb 2022 16:19:21 +0100
Message-ID: <CAC5V6ghxjO7bopsFR3o3ksi-0LhXE0NPbTUXy2b0-mSD+=HTwg@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000001ac97d05d8b0fed0"
Subject: Re: [PHP-DEV] [RFC] Allow null and false as stand-alone types
From: guilliam.xavier@gmail.com (Guilliam Xavier)

--0000000000001ac97d05d8b0fed0
Content-Type: text/plain; charset="UTF-8"

On Sun, Feb 20, 2022 at 6:56 PM G. P. B. <george.banyard@gmail.com> wrote:

> Hello internals,
>
> As a follow up from the "Allow null as a stand-alone type" where the main
> talking point was to also allow false to be used as a stand-alone type, a
> new slightly modified RFC is now proposed:
> https://wiki.php.net/rfc/null-false-standalone-types
>
> The implementation has been updated to reflect the new RFC.
>

The new RFC has a link to implementation and a link to the previous RFC
(which has a link back to the new one) but I had to search for the original
*discussion*, so here it is: https://externals.io/message/116188

(+1 for me, with or without false)

Regards,

-- 
Guilliam Xavier

--0000000000001ac97d05d8b0fed0--