Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104097
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
In-Reply-To: <CAOv67gv0vg=C8hMOiqL_+N=FrD=y1U3XP3v1ocbf+PHO0Ru+Ow@mail.gmail.com>
Date: Mon, 4 Feb 2019 08:33:49 +0100
Cc: PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <B6A4746E-873B-4084-8E4C-B1796CC58460@gmail.com>
References: <CAOv67gv0vg=C8hMOiqL_+N=FrD=y1U3XP3v1ocbf+PHO0Ru+Ow@mail.gmail.com>
To: Wes <netmo.php@gmail.com>
Subject: Re: [PHP-DEV][RFC] Allow void return type variance
From: claude.pache@gmail.com (Claude Pache)


> Le 4 f=C3=A9vr. 2019 =C3=A0 04:22, Wes <netmo.php@gmail.com> a =C3=A9cri=
t :
>=20
> Hello PHPeeps!
>=20
> Recent events convinced me to write this RFC :P
>=20
> Please have a read here https://wiki.php.net/rfc/allow-void-variance
>=20
> I am targeting all the supported PHP versions because this is mainly =
to
> placate the discontent that arised by PHPUnit enforcing its users to =
use
> void, so waiting 7.4 doesn't make much sense.
>=20
> FTR this is an improvement regardless of PHPUnit, and it's IMO a very
> reasonable change.
>=20
> Thank you for your time.
>=20
> Wes


The RFC says: =E2=80=9CChanging from void to something else is very =
probably a bad idea, but PHP should not enforce void in subclasses just =
on that basis.=E2=80=9D =E2=80=94 If it is =E2=80=9Cvery probably=E2=80=9D=
 a bad idea, why do people want to do that? What are the use cases? =
(Sorry, I=E2=80=99ve not followed the =E2=80=9Crecent events=E2=80=9D =
you alludes to.)

=E2=80=94Claude=