Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113464
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
In-Reply-To: <CAPrKfG4u=tXn7qyHUmr4Odgv5oasJ6f9B2tAMsxbn9vSEedBBQ@mail.gmail.com>
Date: Thu, 11 Mar 2021 09:23:51 +0100
Cc: PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <C00CCB6F-9424-4100-AC59-9F8C06F83EA0@stitcher.io>
References: <CAKuGYLRjOHWnX24kCVpTUV5DwdVTwcSkakZkZiAmF9YhpGDpVw@mail.gmail.com>
 <75a8a0ec-d988-7712-58b5-88c8061db605@gmail.com>
 <CAKuGYLR1nNMBNJJXnmmJyDQBf=sFVY0beyv_vT8jBuQMrKpcfg@mail.gmail.com>
 <CAPrKfG4u=tXn7qyHUmr4Odgv5oasJ6f9B2tAMsxbn9vSEedBBQ@mail.gmail.com>
To: Peter Stalman <sarkedev@gmail.com>
Subject: Re: [PHP-DEV] [RFC] noreturn type
From: brendt@stitcher.io (Brent Roose)

Hi Peter and internals

> On 11 Mar 2021, at 07:51, Peter Stalman <sarkedev@gmail.com> wrote:
>=20
> On Wed., Mar. 10, 2021, 11:22 Matthew Brown, =
<matthewmatthew@gmail.com>
> wrote:
>=20
>> If a significant number agree I can add a secondary vote on noreturn =
vs
>> never, but never introduces more of a BC risk.
>>=20
>=20
> Hi Matt,
>=20
> I like this RFC, but I'd like to see the RFC cover if any other =
languages
> have a similar return type.

What made it clear to me was this:

returning nothing (void) isn't the same as not returning (noreturn, eg =
throw or exit).

Having read that somewhere on Twitter made it easier for me to reason =
about. It's a useful feature in the static analysis world.

>=20
> The definition of `void` is that it has no return value, so I too =
agree
> that the keyword `noreturn` is too close in meaning to `void`.
>=20
> I'd also like to throw the word `deadend` or something similar into =
the
> ring, to make things a bit clearer.
>=20
> Thanks,
> Peter

Kind regards
Brent