Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113444
Return-Path: <azjezz@protonmail.com>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 90286 invoked from network); 10 Mar 2021 18:20:05 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 10 Mar 2021 18:20:05 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id E932C1804D1
	for <internals@lists.php.net>; Wed, 10 Mar 2021 10:12:21 -0800 (PST)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 required=5.0 tests=BAYES_00,BODY_8BITS,
	DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,
	RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,
	SPF_PASS autolearn=no autolearn_force=no version=3.4.2
X-Spam-Virus: No
X-Envelope-From: <azjezz@protonmail.com>
Received: from mail-40138.protonmail.ch (mail-40138.protonmail.ch [185.70.40.138])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	by php-smtp4.php.net (Postfix) with ESMTPS
	for <internals@lists.php.net>; Wed, 10 Mar 2021 10:12:20 -0800 (PST)
Date: Wed, 10 Mar 2021 18:12:14 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
	s=protonmail; t=1615399938;
	bh=6Cxw2tSyEbQP5pb3F7+DnmIQtSixAhQJ20v5N7QyqSc=;
	h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From;
	b=iD1SZno0GsgeYl+xT6g7W5upyRe1y8glBrP/M7LCLdA7Dsqglp4WXFLIDu/lhvVEa
	 IL+hygBA6nZGCWvtpzlv/9mstIwR731S2KFXu3c6a+DPQ/KEaCqIRPto3cJEfNJ7z4
	 C+OXvQhZMSr1q87ob/YzXM/3bId4+sXukm9stYv4=
To: Matthew Brown <matthewmatthew@gmail.com>
Cc: Internals <internals@lists.php.net>
Reply-To: Saif Eddin Gmati <azjezz@protonmail.com>
Message-ID: <8OOlCa2SIbJq5b2d_DxDiZTmtfxPki8EiF8DqIGghLxyy1P97RqJpSjs5PtyccxfHI9nDLQ-DbJ5YvMnPZqoAzYIdxHRGf0KtZn54BJSixQ=@protonmail.com>
In-Reply-To: <CAKuGYLRjOHWnX24kCVpTUV5DwdVTwcSkakZkZiAmF9YhpGDpVw@mail.gmail.com>
References: <CAKuGYLRjOHWnX24kCVpTUV5DwdVTwcSkakZkZiAmF9YhpGDpVw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] noreturn type
From: azjezz@protonmail.com (Saif Eddin Gmati)

Hey Matthew,

I have look at the implementation a few days ago, and was patiently waiting=
 for the RFC.

a huge +1 from me ( even tho i can't vote ), `noreturn` type would be a gre=
at addition to PHP type system.


Regards,

Saif.


=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me=
ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90
On Wednesday, March 10, 2021 7:06 PM, Matthew Brown <matthewmatthew@gmail.c=
om> wrote:

> Hey,
>
> Ond=C5=99ej Mirtes and I present an RFC for the noreturn type:
> https://wiki.php.net/rfc/noreturn_type
>
> The feature already exists in Hack (the primary inspiration) and is
> currently supported by our static analysis tools inside docblocks, and we
> feel there's a good argument for it to be supported by PHP itself.
>
> Thanks,
>
> Matt & Ond=C5=99ej