Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113875
MIME-Version: 1.0
References: <CAKuGYLTStzEuOmhGKDdNdWP2iX_--mqV17jub0LgVPs+O6Bd+g@mail.gmail.com>
 <BYAPR05MB547852F3C4ADB69507D1F26CDE7D9@BYAPR05MB5478.namprd05.prod.outlook.com>
In-Reply-To: <BYAPR05MB547852F3C4ADB69507D1F26CDE7D9@BYAPR05MB5478.namprd05.prod.outlook.com>
Date: Tue, 30 Mar 2021 18:24:37 -0400
Message-ID: <CAKuGYLRQksP_3w+P3LeYe2wsf05Qyyn4uEnw=xQotgeecezWHA@mail.gmail.com>
To: Theodore Brown <theodorejb@outlook.com>
Cc: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000054c1f205bec8774b"
Subject: Re: [PHP-DEV] [VOTE] noreturn type
From: matthewmatthew@gmail.com (Matthew Brown)

--00000000000054c1f205bec8774b
Content-Type: text/plain; charset="UTF-8"

On Tue, 30 Mar 2021 at 12:55, Theodore Brown <theodorejb@outlook.com> wrote:

> On Tue, Mar 30, 2021 at 10:06 AM Matthew Brown <matthewmatthew@gmail.com>
> wrote:
>
> > Hey everyone!
> >
> > The vote for adding noreturn is now open:
> >
> > https://wiki.php.net/rfc/noreturn_type
> >
> > Voting will run through April 13th
>
> Hi Matt and Ondrej,
>
> Thanks for your work on this RFC. I voted for `never` as the type name
> because it's more amenable to future use cases like compile-time
> exhaustiveness checks (example:
>
> https://www.typescriptlang.org/docs/handbook/2/narrowing.html#the-never-type
> ).
>
> As a bonus `never` is more concise, avoids mashing two words together,
> and aligns with TypeScript, which I and many other PHP devs also use.
>
> Kind regards,
> Theodore


Awesome! The conciseness argument for "never" is already mentioned in the
RFC, as is TypeScript's use of the term.

Full disclosure (because neither of us is eligible to vote):
I slightly prefer "noreturn", and Ondrej strongly prefers "never".

--00000000000054c1f205bec8774b--