Re: [VOTE] noreturn type
| From: | Matthew Brown | Date: | Tue, 30 Mar 2021 22:24:37 +0000 |
| Subject: | Re: [VOTE] noreturn type | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-113875@lists.php.net to get a copy of this message | ||
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".