Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117357
MIME-Version: 1.0
References: <CAFPFaMJ9mONGwH1McEw-gfmH8KGAG6y9=Fgz-GHcNV0dvVWmJw@mail.gmail.com>
In-Reply-To: <CAFPFaMJ9mONGwH1McEw-gfmH8KGAG6y9=Fgz-GHcNV0dvVWmJw@mail.gmail.com>
Reply-To: Levi Morrison <levi.morrison@datadoghq.com>
Date: Thu, 17 Mar 2022 09:54:26 -0600
Message-ID: <CAAKU0umNUU28xTydO9_xtnHjs9rWpmx+cK0G3eKk7qJGPid5og@mail.gmail.com>
To: "G. P. B." <george.banyard@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] [VOTE] Allow null and false as stand-alone types
From: internals@lists.php.net ("Levi Morrison via internals")

On Sat, Mar 12, 2022 at 10:32 AM G. P. B. <george.banyard@gmail.com> wrote:
>
> 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

Hello,

I have voted yes, despite this clause:

> Moreover, a function which has a void return type must only use return; whereas one with null must use return null;.

IMO, it should allow any expression including just `return;` and let
the runtime fail if it needs to.