Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94891
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.181 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <CANaX5ne1BHOQ4Q8OUPWx-=Sg43zd6L54HZ7DbVzUZniTk9hkKw@mail.gmail.com>
References: <CANaX5ne1BHOQ4Q8OUPWx-=Sg43zd6L54HZ7DbVzUZniTk9hkKw@mail.gmail.com>
Date: Sun, 7 Aug 2016 01:54:33 -0600
Message-ID: <CAFMT4Nru_LMth_pvhBBQBZsODL6tdwJHCcERij8XbzDuRhyj9A@mail.gmail.com>
To: Davey Shafik <me@daveyshafik.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11476e0e4230f20539769c08
Subject: Re: [PHP-DEV] Undocumented Nullable Return Behavior
From: levim@php.net (Levi Morrison)

--001a11476e0e4230f20539769c08
Content-Type: text/plain; charset=UTF-8

On Sun, Aug 7, 2016 at 1:07 AM, Davey Shafik <me@daveyshafik.com> wrote:

> Hi internals,
>
> In the nullable types we do not allow implicit return null/return with no
> value to fulfill a nullable type.
>
> - No return will result in a TypeError when executed
> - Return with no value will be an actual fatal error, which I believe is
> due to the fact it's not found at runtime, should be a TypeError or
> ParseError if possible?
> - Return explicit null is fine (as expected)
>
> See: https://3v4l.org/h6IYF
>
> I believe the first two are contrary to PHP's "null is always returned if
> nothing else is".
>
> OTOH, it makes sense as it's the entire reasoning behind return void vs
> return null.
>
> This behavior is completely undocumented in the RFC.
>
> It's definitely something we should make an explicit decision on for the
> language spec if nothing else.
>
> We should also make any decisions on this prior to beta3 in < 2 weeks.
>
> Thoughts?
>
> - Davey
>

hello_2 looks particularly fishy to me; to my knowledge we did not pass any
RFCs that would dictate such a message. However I have not been as active
as I'd like to be so perhaps I just missed it.

--001a11476e0e4230f20539769c08--