Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104101
MIME-Version: 1.0
References: <CAOv67gv0vg=C8hMOiqL_+N=FrD=y1U3XP3v1ocbf+PHO0Ru+Ow@mail.gmail.com>
 <B6A4746E-873B-4084-8E4C-B1796CC58460@gmail.com>
In-Reply-To: <B6A4746E-873B-4084-8E4C-B1796CC58460@gmail.com>
Date: Mon, 4 Feb 2019 09:00:42 +0100
Message-ID: <CAOv67guJw8E3eWe6aoLchQGZ4Mb5iYptobqO=T=oSJ+WYKo-9g@mail.gmail.com>
To: Claude Pache <claude.pache@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000082a30205810cda89"
Subject: Re: [PHP-DEV][RFC] Allow void return type variance
From: netmo.php@gmail.com (Wes)

--00000000000082a30205810cda89
Content-Type: text/plain; charset="UTF-8"

Hi!

PHPUnit 8 changed e.g.  `  function setUp(){}` to  `  function setUp():
void{} `   and a lot of people did not like being forced to do the same on
their  `setUp()`.

The issue is not PHPUnit adding `void`, but PHP forcing `void` even when
it's not necessary. If PHPUnit wants to use void but inheritors don't want
to, it should just be possible.

"probably a bad idea" is opinionated, in reality there is no provable
reason to disallow it, from a pure type-theory standpoint.

--00000000000082a30205810cda89--