Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117358
MIME-Version: 1.0
References: <CAFPFaMJ9mONGwH1McEw-gfmH8KGAG6y9=Fgz-GHcNV0dvVWmJw@mail.gmail.com>
 <CAAKU0umNUU28xTydO9_xtnHjs9rWpmx+cK0G3eKk7qJGPid5og@mail.gmail.com>
In-Reply-To: <CAAKU0umNUU28xTydO9_xtnHjs9rWpmx+cK0G3eKk7qJGPid5og@mail.gmail.com>
Date: Thu, 17 Mar 2022 16:09:00 +0000
Message-ID: <CAFPFaM+08T_DpaY9ujsrWJkW6--01TY5n6wMA=N7KR8FBcA50w@mail.gmail.com>
To: Levi Morrison <levi.morrison@datadoghq.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000002aa74e05da6c403d"
Subject: Re: [PHP-DEV] [RFC] [VOTE] Allow null and false as stand-alone types
From: george.banyard@gmail.com ("G. P. B.")

--0000000000002aa74e05da6c403d
Content-Type: text/plain; charset="UTF-8"

On Thu, 17 Mar 2022 at 15:54, Levi Morrison <levi.morrison@datadoghq.com>
wrote:

> 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.
>

This behaviour is the current behaviour in PHP, see:
https://3v4l.org/1m0Mk
and
https://3v4l.org/d19rd

It might make sense to change this, but this is out of scope for this RFC.

Best regards,

George P. Banyard

--0000000000002aa74e05da6c403d--