Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113463
To: internals@lists.php.net
References: <CAKuGYLRjOHWnX24kCVpTUV5DwdVTwcSkakZkZiAmF9YhpGDpVw@mail.gmail.com>
 <e397c220-13cb-6055-3e1e-3aaf3ee18ae9@alec.pl>
 <F06253BB-9B2C-49DC-B382-A222506E2F26@benramsey.com>
Message-ID: <a3360baf-0dfa-1170-6303-0f7fc365ba41@alec.pl>
Date: Thu, 11 Mar 2021 08:24:58 +0100
MIME-Version: 1.0
In-Reply-To: <F06253BB-9B2C-49DC-B382-A222506E2F26@benramsey.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] noreturn type
From: alec@alec.pl (Aleksander Machniak)

On 10.03.2021 20:28, Ben Ramsey wrote:
>> I don't like that type covariance would be allowed. Why such an
>> exception to the rules?
> 
> It’s not an exception. Returns are covariant. Parameters are
> contravariant. Since `noreturn` is a subtype of all other types, it
> behaves as expected.

I see it's a subtype, I don't get why. Wouldn't it be better to be a
separate type so return type covariance is not allowed (as it is with
void)? Was it a design decision or a side product of the implementation?

-- 
Aleksander Machniak
Kolab Groupware Developer        [https://kolab.org]
Roundcube Webmail Developer  [https://roundcube.net]
----------------------------------------------------
PGP: 19359DC1 # Blog: https://kolabian.wordpress.com